Re:Chrome 14 released
by aboodman on Friday September 16, 2011 @02:13PM
(#3005584)
I think the release managers usually unlock security bugs for a release once most of the population has been updated. So check back in a few days to a week.
[ Parent
| on HN ]
66560 is a webkit issue. Webkit is an open source project. Webkit vulnerabilities are not disclosed until all the other consumers like Safari are updated.
Re:Chrome 14 released
by simonbrown on Friday September 16, 2011 @02:32PM
(#3005667)
The blog posts mention that the bugs are only kept private until most people are up to date, but some never seem to be made public. For example:
http://googlechromereleases.blogspot.com/2011/01/chrome-stab...
Some of the bugs (e.g. 66560) still give me a 403 (although some are accessible).
Of the 15 bugs there, 9 are open now. I'll poke someone more knowledgable and ask them to explain why the others have not been opened.
I could imagine that it's that the process for unlocking them is manual and easy to forget, or it could be that other instances of those bugs were uncovered so it still isn't safe to open them.
aayra (who replied to great-grandparent) works on Chrome security team. It looks like all the bugs that are still closed are WebKit bugs (css, svg, etc), and we don't open them until the other WebKit clients are updated.