Post #2633401
2026-01-01 02:22 UTC
@ravigupta@mastodon.social @julienw@pouet.chapril.org @gruber@mastodon.social Chrome has an autoupdater. Given that we’re an app that handles data from the internet, we need to stay up-to-date for security’s sake. But Chrome hasn’t used Keystone in quite a while. We switched to an open-source updater and you’re welcome to look it over. https://source.chromium.org/chromium/chromium/src/+/main:chrome/updater/
Replies (1)
-
@ravigupta@mastodon.social 2026-01-01 02:35
@avidrissman@mas.to @julienw@pouet.chapril.org @gruber@mastodon.social Every other browser stays secure without having a persistent background updater, Chrome is not unique in having to handle data from the Internet. Chrome may download updates while the browser is not running but those won’t be applied until the user clicks ‘Update’ in the UI. How is it more secure than downloading the update while the browser is running? A fresh Chrome install still drops the Keystone binaries around macOS. If it doesn’t use them why place them?