fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-10 00:12:09 +00:00
Code Issues Projects Releases Wiki Activity

Compare commits

base: fmaury:dea7ebf05a6c8d140aa55c4e05027131a4851bd7
Branches Tags
fmaury:master
fmaury:draft-searchengines
..
compare: fmaury:b07f06e00989a4688cae8dc01ca559a8aa59825c
Branches Tags
fmaury:master
fmaury:draft-searchengines

No commits in common. "dea7ebf05a6c8d140aa55c4e05027131a4851bd7" and "b07f06e00989a4688cae8dc01ca559a8aa59825c" have entirely different histories.
dea7ebf05a ... b07f06e009

1 changed files with 0 additions and 25 deletions
Show stats Expand all files Collapse all files

25
content/notes/caveats-to-ungoogled-chromium-recommendations.md
View file

@ -1,25 +0,0 @@
---
title: "Caveats to Ungoogled Chromium recommendations"
date: 2024-07-15T00:05:38-04:00
syndicatedCopies:
- title: 'The Fediverse'
url: 'https://pleroma.envs.net/objects/b4de6133-3e88-448a-a795-874d285e56da'
- title: 'jstpst'
url: 'https://jstpst.net/f/technology/10291/caveats-to-ungoogled-chromium-recommendations'
---
In the wake of a certain ad-funded browser company bundling adtech into its browser yet again, some people have been recommending Ungoogled-Chromium (<abbr>UGC</abbr>). I think it's fine to recommend <abbr>UGC</abbr> _with caveats,_ such as the fact that it disables component updates that include:
- Certificate revocation. Chromium uses [downloaded CRLSets](https://www.chromium.org/Home/chromium-security/crlsets/) for revocation; it does not support OCSP.
- Out of band security patches. When browser components have exploits in the wild, they need to be patched ASAP; updating billions of installations within time-frames measured in hours often means restartless out-of-band updates.
- Out of band certificate bundle updates.
If you assume Google uses its component update server logs maliciously, you may wish to consider a fork that still offers component updates provided by a different party's servers.
<abbr title="Ungoogled Chromium">UGC</abbr> disabled mDNS at one point. This exposed local IP addresses over WebRTC for years, but they seem to have shipped a fix in May 2023 to disable non-proxied UDP.
<abbr>UGC</abbr> also disables the Chrome Web Store in favor of installing extensions out of band. Make sure you regularly update your extensions installed out-of-band, since <abbr>UGC</abbr> won't do it on its own. Some scripts and a special extension re-implement some of this functionality.
Overall, <abbr>UGC</abbr> is still safer than QtWebEngine despite making heavy compromises to security for privacy (though I can't see how either benefited from disabling mDNS: I'm not aware of threat models under which revealing a local IP to every application is preferable to revealing it to just Google). Running <abbr>UGC</abbr> is fine if you understand these trade-offs and have accounted for them. I use it in headless mode to run accessibility and performance tests.