3 ms·
One could argue, especially considering some of the disclosure situations surrounding Project Zero that have occurred, that it exists more to shame competitors
by ocdtrekkie 10y ago
One could argue, especially considering some of the disclosure situations surrounding Project Zero that have occurred, that it exists more to shame competitors than improve the world. :) To my knowledge, only like once have I heard the words "Project Zero" in relation to a flaw in Google software.
But as Google definitely does do security testing on competitors' products such as Windows, it definitely goes to show that Google would be more than happy to test for security flaws in Firefox. And regardless of Google's motives, finding security flaws does, in the end, make a more secure Internet for everybody.
- halbecaf 10y agoProject Zero has reported plenty of bugs in Google software: https://bugs.chromium.org/p/project-zero/issues/list?can=1&q=vendor%3AGoogle https://bugs.chromium.org/p/project-zero/issues/list?can=1&q...
- username223 10y agoThat's encouraging -- I had cynically assumed it was just a naive PR play -- but have they screwed over other Google projects by publishing 0-days at the end of their arbitrary time window? For example, do they publish zero-days on widely-deployed versions of Android?
- dgacmu 10y agoI believe they follow the same reporting process regardless of vendor, Google included. Here's one that Google fixed in Chrome about 15 days before the 90 day public release threshold: https://bugs.chromium.org/p/project-zero/issues/detail?id=162&can=1&q=&start=100 https://bugs.chromium.org/p/project-zero/issues/detail?id=16... (You'll note the explicit discussion in there about the deadline: "Chromium issues should be treated the same as any others. So there's a 90-day deadline (which was not exceeded in this case), ... Same disclosure warning to the Chrome team was in this bug: https://bugs.chromium.org/p/project-zero/issues/detail?id=513&can=1&q=&start=400 https://bugs.chromium.org/p/project-zero/issues/detail?id=51... And project zero explicitly warned the Android team about the 90 day disclosure policy in the one bug report I checked: https://code.google.com/p/android/issues/detail?id=182510 https://code.google.com/p/android/issues/detail?id=182510 Edited to add: Here's one where they disclosed prior to Android fixing the bug: https://bugs.chromium.org/p/project-zero/issues/detail?id=860&q= https://bugs.chromium.org/p/project-zero/issues/detail?id=86... with the note "deadline exceeded". Unfortunately, the link to the Android bug is still protected, so we can't learn why AOSP hasn't fixed it yet.