Chrome Stable channel updated

Chrome 20 (aka dental floss' release, lmao) shows that version numbering definitely lost any importance to typical Chrome's users. This is a bit disappointing, although fully expected.

 

If you insist. I don't really care lol some releases hold new features and some releases hold improvements to old ones.

 

Typically, devs would try to impress the crowd in the "divisible by ten" numbered releases. It's weird to see this "typical behavior" getting lost in this project.

 

Well, except for the security fixes, there's a subtle UI change with the larger new tab button. But the the most important change in Chrome 20 for me is the untrusted integrity level.

 

go go chrome

 

Where can one find more info on the untrusted integrity level change, JimboW?

 

Sorry, I haven’t come across any Chrome articles referencing it. However we already know how good Chrome was with a low IL, well untrusted is even stricter as to what can be done to the system. The in-built PDF is now already running as untrusted and I’m guessing over the next few versions we’ll be using pepper flash as you can already use it in the dev channel. And because pepper flash runs in the Chrome sandbox it will be running as untrusted which is great against any potential flash exploits whilst also eliminating the need for the medium IL broker process currently in use (not needed with pepper flash). Some of us don’t use an AV or the like, so I don’t just look at Chrome as a browser but also as a security program, so any hardening of Chromes already impressive sandboxing structure is welcomed.

 

But I'm saying, where is there info that confirms that the untrusted integrity level change happened in Chrome 20?

 

None that I'm aware of, but you can see it with Process Explorer.

 

TY

 

confirmed.

on my machine the Google children/sub-processes are running as "Untrusted" instead of "Low" like they were before.

i don't know the difference between the two but "Untrusted" sounds a lot safer than "Low".

 

I looked at about:flags after quite a few months and the list is much longer than I remember. I was looking to turn on click-to-play because I remember it being in about:flags but it wasn't there. Turns out it's been made regular but I don't know in which Chrome version this happened.

 

Low Integrity means that the process can write to low integrity files and folders. Untrusted Integrity means that the process can only write to untrusted files and folders - there are no untrusted files/ folder by default therefor Chrome's renderer no longer has any write access to the system.

There are more changes to the sandbox coming soon.

@Vasa,

That was a while back.

This version contained hundreds of bug fixes.

 

@HM, I thought you'd be busy keeping an eye on things over at Google I/O.

 

The Beta and Stable channel has been updated to 20.0.1132.47 for Windows, Mac, Linux, and Chrome Frame. This release disables some of Chrome’s GPU acceleration features on Mac hardware containing the Intel HD 4000 graphics chip (e.g. the new Macbook Airs), in order to prevent a resource leak which is causing a kernel panic on that hardware. This is a temporary change while we work on fixing the root cause of the issue.

 

And that means at least one more update in the pipes on this issue. Some Linux users are having problems as well with Chrome 20: for some of them, Chrome won't start and they see zombies instead; for others, Flash is a problem.
I've turned off updates until something necessary comes around because Chrome 20 is working just fine for me.

 

I wonder how frequently both the Beta and Stable channels are simultaneously updated to the same version number? Probably not very often.

20 is doing fine for me as well. In the (almost) one year that I have been using Chrome as my default browser, I have never experienced a problem with an update.

 

seems like a 'minor' update, from what i can gather:

 

It's not uncommon for a few days immediately following the release of a stable version that both stable and beta have the same version number.

 

Yes, I agree, but that is not what happened.
Both the stable and the beta were simultaneously updated at the same time to the same number...

See what I mean?

 

The Stable channel has been updated to 20.0.1132.57 for Windows, Mac, Linux, and Chrome Frame.

Along with below mentioned security fixes, this build contains an update to Flash player, v8 (3.10.8.20) and couple of stability/bug fixes.

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.

[$1000] [129898] High CVE-2012-2842: Use-after-free in counter handling. Credit to miaubiz.
[$1000] [130595] High CVE-2012-2843: Use-after-free in layout height tracking. Credit to miaubiz.
[133450] High CVE-2012-2844: Bad object access with JavaScript in PDF. Credit to Alexey Samsonov of Google.

 

From The H Open

 

The Stable channel has been updated to 21.0.1180.57 for Mac and Linux and 21.0.1180.60 for Windows and Chrome Frame. Chrome 21 contains a number of new features including a new API for high-quality video and audio communication.