Google has just let loose the via Dev channel an updated build of its fast-paced browser, Chrome. According to its makers, Chrome 4.0.206.1, which can be downloaded from this page, features:
All Platforms
– Closing the download shelf removes all completed and cancelled downloads from it. (Issue: 15712)
– Fixes various audio/video events which were not firing. (Issues: 20152, 16768)
– Saved passwords for proxy servers are now correctly labeled. (Issue: 12992)
– Add single line of tips to New New Tab Page. (Issue: 19162)
Mac
– HTTP Auth dialog autofills passwords.
– New Tab Page displays much faster. (Issue 13337)
– Improved scrolling and display performance, particularly on machines without powerful graphics hardware (such as laptops)
– Plugins starting offscreen will draw correctly when they scroll into view (Issue 20234)
Linux
– HTTP Auth dialog autofills passwords.
– Fix the find bar so the match count is inside the entry. (Issue: 17962)
– Now respects both GNOME and KDE proxy settings. (Issue: 17363)
– Implemented "Confirm form resubmission" dialog. (Issue: 19761)
– Don’t paste primary selection when middle clicking scrollbars. (Issue: 16400)
– Fix inability to select Times New Roman in font options with some versions of Pango. (Issue: 19823)
– Fixed tab dragging on 64-bit. (Issue: 20513)
– Fixed 64-bit JavaScript crash on some CPUs. (Issue: 20789)
Extensions
– Two breaking changes (see mailing list post for more information):
– Enforce granular permissions
– Modified several APIs to be more consistent
– Polish the look of Linux extension shelf. (Issue: 16759)
– Polish extension install UI.
– Allow extension toolstrip to detach. (ctrl+alt+b)
– Polish chrome://extensions/ page. Add convenience developer tools to load an extension and pack an extension.
What's New
The stable channel has been updated to 3.0.195.32, and includes the following security and stability fixes:
· Resolved a history issue that affected going back from queries in Google Maps. (Issue: 21353)
· Fixed issue with Adobe Acrobat Reader 9.2, where no content would be displayed. (Issue: 24883)
· Fixed an infinite loop in acc decoding. (Webkit Issue: 27239)
· Fixed a top crasher. (Issue: 22205)
· Fix issues where setInterval sometimes eating 100% CPU. (Issue: 25892)
Security Fixes:
· CVE-2009-XXXX User not warned for some file types that can execute JavaScript
· The user was not warned about certain possibly dangerous file types such as SVG, MHT and XML files.In some browsers, JavaScript can execute within these types of files. Because the JavaScript runs in the local context, it may be able to access local resources.
· More info: http://code.google.com/p/chromium/issues/detail?id=23979
· (This issue will be made public once a majority of users are up to date with the fix.)
· Severity: Medium
· Credit: Inferno of SecureThoughts.com
Mitigations:
· A victim would need to visit a page under an attacker's control.
· The victim would furthermore need to open a malicious file.
· CVE-2009-XXXX Possible memory corruption in the Gears plugin
· A malicious site could use the Gears SQL API to put SQL metadata into a bad state, which could cause a subsequent memory corruption. This may lead to a Gears plugin crash or possibly arbitrary code execution.
· More info: http://code.google.com/p/chromium/issues/detail?id=26179
· (This issue will be made public once a majority of users are up to date with the fix.)
· Severity: High
· Credit: This issue was found by the Google Chrome security team.
Mitigations:
· A victim would need to visit a page under an attacker's control.
· The victim would furthermore need to "click-through" the Gears dialog confirming that they trust the attacker's evil page