Re:Critical Google Chrome hole plugged in 24 hours
by jamesr on Friday March 09, 2012 @12:56AM
(#3683095)
The commits are all there, the fixes just might not look completely obvious. We (chromium) commit all fixes to the chromium repository before pushing them to users, always.
Re:Critical Google Chrome hole plugged in 24 hours
by vinhboy on Friday March 09, 2012 @01:23AM
(#3683154)
Do you guys ever do write-ups about the bugs? I would be interested in reading that.
Re:Critical Google Chrome hole plugged in 24 hours
by jamesr on Friday March 09, 2012 @01:30AM
(#3683170)
I don't think we do that as a general habit, but that may happen in this case.
Re:Critical Google Chrome hole plugged in 24 hours
by emmelaich on Friday March 09, 2012 @08:25PM
(#3686730)
My wild-arsed guess is: http://src.chromium.org/viewvc/chrome/branches/963/src/conte...
-- a change to kUnreachableWebDataURL
Re:Critical Google Chrome hole plugged in 24 hours
by palish on Thursday March 08, 2012 @11:28PM
(#3682915)
Well... They would hopefully be smarter than committing the fix to the public SVN.
By committing the fix, they would effectively be releasing a step-by-step guide on how to exploit the vulnerability.
Re:Critical Google Chrome hole plugged in 24 hours
by semenko on Thursday March 08, 2012 @11:50PM
(#3682969)
But it's still an open source project -- perhaps the commits are more evident in their git repo? http://git.chromium.org/gitweb/
Certainly if you build Chromium from git/SVN now, the bug is fixed.
I just find it a little strange that their changelog / list of commits in each version is not true.
And that the SVN commit history is available: http://build.chromium.org/f/chromium/perf/dashboard/ui/chang...
But I don't see any commit that look even remotely related to this exploit. What's up?