Post

Something completely underappreciated in how Google Chrome revolutionized the web and security and software in general — was the silent background auto-update + and non-admin user-level installs. It set a bar that changed everything on ability to make progress & address threats. Broke IT paradigms.

When Chrome came out, IT admins kept asking how it was possible users were installing it without admin? That's because they did not really understand the system. Developers and attackers in XP days were so used to users having admin they rarely bothered trying to make anything work without it.

However, Chrome was happy to install its files in the user's own profile, not the system level-level directories needing admin. You can do anything you want in your own profile. Chrome set up shop, slapped shortcuts on Desktop and Start Menu, there's no user-exposed difference in the end result.

Omg commentary from someone who was there at Google! I was going to get around to Omaha but it's possibly too in-the-weeds. It's unfortunate so many rely on weaker less mature and secure update system alternatives to it, but they are dumb-simple. bsky.app/profile/h.ol...

Joe Beda@h.olysh.it

We actually started this with the Windows Google Talk client. We wanted a native app that had a lifecycle similar to the web. The update code got pulled out as a project called Omaha (github.com/google/omaha) and was then used in Chrome.

Yes! How Google taking absolute end to end ownership of update results was an incredible bar to raise. No more blaming users they hit the update button when something breaks, or didn't when they were hacked. You have to own the entire lifecycle including breaking changes. bsky.app/profile/h.ol...

Joe Beda@h.olysh.it

Of course! More lore: Auto update is *hard*. If you get it wrong you either strand users on old versions or turn it into a DDOS against your update servers.

Most people talking about Chrome's innovations would first highlight the security sandboxing and V8 JavaScript, but it was truly a revolutionary epoch in ecosystem norms. Or, why don't you hear about PDF hacks much anymore? ~Adobe adopted Chrome sandbox code. (Fun fact IE7 had sandbox long story)

3 reposts95 likes