Thema: Chrome / Chromium / Iron Browser ....

[SiLæncer]

The Dev channel has been updated to 25.0.1337.0 for Windows, Mac, and Chrome Frame.  A full list of changes in this build is available in the SVN revision log.

http://googlechromereleases.blogspot.co.il/2012/11/dev-channel-update_28.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Stable channel has been updated to 23.0.1271.95 for Windows, Mac, Linux, and ChromeFrame 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.

    [161564] High CVE-2012-5138: Incorrect file path handling. Credit to Google Chrome Security Team (Jüri Aedla).
    [$7331] [162835] High CVE-2012-5137: Use-after-free in media source handling. Credit to Pinkie Pie.


Congratulations to Pinkie Pie for completing challenge: 64-bit exploit.

Many of the above bugs were detected using AddressSanitizer.

Full details about what changes are in this release are available in the SVN revision log.

http://googlechromereleases.blogspot.co.uk/2012/11/stable-channel-update_29.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Beta channel has been updated to 24.0.1312.27  for Windows, Mac, Linux, and Chrome Frame.  This build contains following updates:

    Fixed random Chinese/Japanese characters that are missing in documents printed via the system print dialog on Windows XP SP3. [Issue: 128506]
    Fixed memory leak in  GPU accelerated canvas. [Issue: 160411]
    Fixed console.log which doesn’t output jQuery objects properly. [Issue: 162570]
    Fixed stability issues like 161854, 154483, 154462, 153376.


Full details about what changes are in this build are available in the SVN revision log.

http://googlechromereleases.blogspot.co.uk/2012/11/beta-channel-update_29.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Beta channel has been updated to 24.0.1312.32  for Windows, Mac, Linux, and Chrome Frame.  This build contains following updates:

    Fixed crashes like 161858, 158747, 156878
    Fixed graphical corruption in Dust. [Issue: 155258]
    Fixed print preview in Windows 8 mode. [Issue: 159902]
    Fixed scrolling issue. [Issue: 163553]


Full details about what changes are in this build are available in the SVN revision log.

http://googlechromereleases.blogspot.com/2012/12/beta-channel-update.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Dev channel has been updated to 25.0.1349.2 for Windows, Mac, Linux, and Chrome Frame. A full list of changes in this build is available in the SVN revision log.

http://googlechromereleases.blogspot.com/2012/12/dev-channel-update.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Beta channel has been updated to 24.0.1312.36 for Mac; 24.0.1312.35 for Windows, Linux, and Chrome Frame. This build contains fixes for stability. Full details about what changes are in this build are available in the SVN revision log.

http://googlechromereleases.blogspot.com/2012/12/beta-channel-update_6.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Dev channel has been updated to 25.0.1354.0 for Windows, Mac, Linux, and Chrome Frame.  This build includes a test of new variations of the New Tab Page for a small set of users.  A full list of changes in this build is available in the SVN revision log.

http://googlechromereleases.blogspot.co.uk/2012/12/dev-channel-update_10.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Stable channel has been updated to 23.0.1271.97 for Windows, Mac, Linux, and ChromeFrame platforms. This build contains the following fixes:

    Some texts in a Website Settings popup are trimmed (Issue: 159156)
    Linux: <input> selection renders white text on white bg in apps (Issue: 158422)
    some plugins stopped working (Issue: 159896)
    Fixed a known crash (Issue:161854)


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.

    [$1500] [158204] High CVE-2012-5139: Use-after-free with visibility events. Credit to Chamal de Silva.
    [$1000] [159429] High CVE-2012-5140: Use-after-free in URL loader. Credit to Chamal de Silva.
    [160456] Medium CVE-2012-5141: Limit Chromoting client plug-in instantiation. Credit to Google Chrome Security Team (Jüri Aedla).
    [160803] Critical CVE-2012-5142: Crash in history navigation. Credit to Michal Zalewski of Google Security Team.
    [160926] Medium CVE-2012-5143: Integer overflow in PPAPI image buffers. Credit to Google Chrome Security Team (Cris Neckar).
    [$2000] [161639] High CVE-2012-5144: Stack corruption in AAC decoding. Credit to pawlkt.



This build also has a new version of Adobe Flash. You can find the details here.

Full details about what changes are in this release are available in the SVN revision log.

http://googlechromereleases.blogspot.co.uk/2012/12/stable-channel-update.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Beta channel has been updated to 24.0.1312.40  for Windows, Mac, Linux, and Chrome Frame.  This build contains stability fixes. Full details about what changes are in this build are available in the SVN revision log.

http://googlechromereleases.blogspot.ca/2012/12/beta-channel-update_12.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Dev channel has been updated to 25.0.1359.3 for Windows, Mac, Linux, and Chrome Frame. This update contains a number of stability fixes. A full list of changes in this build is available in the SVN revision log.

http://googlechromereleases.blogspot.com/2012/12/dev-channel-update_13.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Dev channel has been updated to 25.0.1364.2 for Windows, Mac, Linux, and Chrome Frame. This update contains additional stability fixes. A full list of changes in this build is available in the SVN revision log.

http://googlechromereleases.blogspot.pt/2012/12/dev-channel-update_18.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Beta channel has been updated to 24.0.1312.45  for Windows, Mac, Linux, and Chrome Frame.  This build contains stability fixes. Full details about what changes are in this build are available in the SVN revision log.

http://googlechromereleases.blogspot.com/2012/12/beta-channel-update_19.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

The Dev channel has been updated to 25.0.1364.5 for Windows, Mac, Linux, and Chrome Frame. This update contains stability and memory fixes. A full list of changes in this build is available in the SVN revision log.

http://googlechromereleases.blogspot.pt/2012/12/dev-channel-update_20.html

Download :

Google Chrome Finalversion: http://www.google.com/chrome
Google Chrome Betaversion: http://www.google.com/landing/chrome/beta/
Google Chrome Developer: http://www.google.com/chrome/eula.html?extra=devchannel

[SiLæncer]

Bislang war es möglich, bei der Windows-Version von Googles Webbrowser Chrome Erweiterungen im Stillen zu installieren. Dies wird zukünftig nicht mehr möglich sein. Zur Begründung erklären die Chrome-Entwickler, das Feature sei in der Vergangenheit vielfach von Entwicklern missbraucht worden, um Nutzern gegen deren Willen unnötige oder gar schädliche Erweiterungen unterzuschieben.

Der ganze Artikel

Quelle : www.gulli.com

[Jürgen]

Installiert ein Drittanbieter-Programm eine Chrome-Erweiterung, erscheint in Zukunft ein Chrome-Menü, in dem Benutzer auswählen können, ob sie die Erweiterung aktivieren oder deinstallieren möchten.

Diesen Ansatz halte ich für vollkommen verfehlt und ein nicht geringes Sicherheitsrisiko.
Ein unerbetener Download ist schon allein verdächtig, eine bereits im Hintergrund durchgeführte Installation mit erst anschließender Nachfrage zu Aktivierung oder Entfernen ist ein Unding.
Immerhin ist nicht sichergestellt, ob so nicht schon einige Teile eines Plugins außerhalb des Browsers aktiv werden und z.B. die Registry nachhaltig manipulieren.
Und Zero-Day-Exploits könnten so schon direkt greifen, noch bevor der Nutzer irgendetwas ablehnen kann.
Ich bin sicher, über kurz oder lang hören wir davon...

Für wesentlich vernünftiger würde ich halten, wenn bei Feststellung eines "fehlenden Plugins" NICHTS automatisch abläuft, außer einer Anfrage an den Nutzer, ob er dieses herunterladen und installieren möchte.
Andere Browser-Hersteller können das ja auch.
Erst fragen, dann ggf. holen!

Jürgen