Dall´inizio dell´anno, i bug critici risolti da Google in Chrome sono stati ben cinque. La soluzione alle problematiche più gravi viene accreditata agli sviluppatori di Google, mentre il bug definito importante è stato risolto da un freelance esterno, il quale ha intascato 1.000 dollari di ricompensa. Neanche male direi.

Ecco le note ufficiali.

Changelog:

The Stable channel has been updated to 11.0.696.71 for the Macintosh, Windows, Linux and Chrome Frame platforms

Security fixes and rewards:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

[72189] Low CVE-2011-1801: Pop-up blocker bypass. Credit to Chamal De Silva.
[$1000] [82546] High CVE-2011-1804: Stale pointer in floats rendering. Credit to Martin Barbella.
[82873] Critical CVE-2011-1806: Memory corruption in GPU command buffer. Credit to Google Chrome Security Team (Cris Neckar).
[82903] Critical CVE-2011-1807: Out-of-bounds write in blob handling. Credit to Google Chrome Security Team (Inferno) and Kostya Serebryany of the Chromium development community.


The following bugs were fixed:
REGRESSION: selection extended by arrow keys flickers on LinkedIn.com. (Issue83197).
Have ConnectBackupJob try IPv4 first to hide potential long IPv6 connect timeout (Issue81686).
Mac plugin crashes are too low in stats (Issue 82172).
Incorrect ACLs on the archived copy of setup.exe (Issue 82424)


If you find new issues, please let us know by filing a bug => http://code.google.com/p/chromium/issues/entry

Want to change to another Chrome release channel? Find out how => http://dev.chromium.org/getting-involved/dev-channel



DOWNLOAD UPDATE CHROME