News for hackers. Stuff that matters.
Re:Google has added ads on both its search page and Chrome:/... by Caboose8685 on Friday September 30, 2022 @09:54AM (#33034856)
It's worth noting that UGC has some significant security regressions

https://qua3k.github.io/ungoogled/

Re:Google has added ads on both its search page and Chrome:/... by 2kwatts on Friday September 30, 2022 @10:18AM (#33035168)
When I need to use a Chrome-like browser, I just use Chromium or Brave.
Re:Google has added ads on both its search page and Chrome:/... by 2Gkashmiri on Friday September 30, 2022 @12:50PM (#33037260)
and people will still not recommend firefox. this is hilarious
Re:Google has added ads on both its search page and Chrome:/... by lcnPylGDnU4H9OF on Friday September 30, 2022 @05:07PM (#33040828)
Firefox is my daily driver but if something "works best in Chrome" I (assuming I'm interested enough) open it in Brave.
Re:Google has added ads on both its search page and Chrome:/... by fulafel on Saturday October 01, 2022 @02:53AM (#33044555)
Is there evidence that Brave or your preferred Chromium build reproduce the compiler etc tooling that official Chrome supposedly uses for speedbumps to hinder exploiting their memory safety vulnerabilities?
Re:Google has added ads on both its search page and Chrome:/... by bentcorner on Friday September 30, 2022 @10:48AM (#33035636)
Interesting to learn. Are these issues fixable? I'm not familiar with what changes went into UGC but something like changing the compiler toolchain seems like a strange decision.
Re:Google has added ads on both its search page and Chrome:/... by TingPing on Friday September 30, 2022 @11:15AM (#33036000)
Upstreams toolchain is pretty insane so most downstream try to do the more default thing but that often doesn't include the same customizations.

I think its all doable but community forks tend to be one person doing a job of 10 people and will never keep up.

Re:Google has added ads on both its search page and Chrome:/... by account42 on Thursday October 06, 2022 @09:23AM (#33107867)
> Security Updates

> The component updater, responsible for delivering out-of-band security updates to the various components of the browser, is disabled within ungoogled-chromium. It’s responsible for updating Chrome’s CRLSets, which are necessary for meaningful certificate revocation. Most of the components are delivered via the component updater because they have a need for out-of-band security updates, and it’s not helpful nor necessary to disable them.

> Furthermore, the extensions that users rely on aren’t updated automatically, posing an additional risk to users of the browser.

Not connecting to google services unles you explicitly request it is almost the entire point of ungoogled-chromium, so this is really misplaced criticism. Especially for the CRLs, giving Google the power to take third party websites offline is not something everyone agrees with.

The missing hardening is also not something to be summed up as "significant security regressions". Ironically it might even improve your security if it means that attacks depending on Chromes upstream toolchain configuration won't work - no one is realistically going to specifically target a niche project like ungoogled-chromium.