CrashKill/2014-06-09: Difference between revisions
Jump to navigation
Jump to search
m (→Desktop) |
m (→Desktop) |
||
| Line 16: | Line 16: | ||
{{bug|1022471}} Conduit SearchProtect has started disabling our DLL blocklist. Signatures like libinject and MovieMode are coming back. What can we do? Our usual approach doesn't work against a determined adversary. | {{bug|1022471}} Conduit SearchProtect has started disabling our DLL blocklist. Signatures like libinject and MovieMode are coming back. What can we do? Our usual approach doesn't work against a determined adversary. | ||
* see questions/ | * see questions/concerns below in beta section. | ||
===Beta=== | ===Beta=== | ||
Revision as of 15:25, 9 June 2014
General
- Numbers on http://arewestableyet.com/ and KaiRo's long-term graphs are very late almost every day because of bug 1010257 (scheduling issue in Socorro).
Previous Action Items
- [Carryover] KaiRo/liz to evaluate options for public stability list. KaiRo sent an email to Liz, didn't a get a reply yet.
- bug 883134:
- juanb to be on point to get reproducible case with community
- bsmedberg to talk to johns to look into it
- KaiRo to ask relman to contact GAS Tecnologia
- bsmedberg to find nightly regression range for bug 768395
Socorro
Flash
Desktop
bug 1022471 Conduit SearchProtect has started disabling our DLL blocklist. Signatures like libinject and MovieMode are coming back. What can we do? Our usual approach doesn't work against a determined adversary.
- see questions/concerns below in beta section.
Beta
- bug 1022471 - Conduit SearchProtect disables the blocklist
- We were looking pretty good for 30 stability. But this bug is destabilizing 30. If the volume of crashes in libinject.dll returns to the level we had in early 30 betas, 30 is going to be the crashiest release we've put out in a while. :-(
- Do A/V vendors typically battle these sorts of things? If so, have we made them aware?
- If not, is there anything we can do to mitigate this without a respin, right now? Can we even turn around an RC build 3 in under 24 hours, if we had to? It doesn't seem prudent to try. Which leaves us putting out a point release with a fix that may be fleetingly effective at best.