Haven’t used Ungoogled Chromium in a couple years, but I’ve seen some criticisms of it even compared to regular Chrome: https://qua3k.github.io/ungoogled/
Thank you for sharing this, I was unaware. I wonder if any of this has been addressed recently as the linked article is two years old (not demeaning its value, just wondering if the devs saw the article and decided to improve ungoogled-chromium).
Yeah, that’s why I pointed out that I haven’t used it in a couple years, I have no idea about the direction development took after that, so maybe some folks that work on the development of Chromium and its many forks can give us some insight. Personally, I just decided to stick to Firefox tweaked with Arkenfox as my main browser on desktop and I have Brave with all its annoyances turned off as a backup option
No one is going to develop exploits only for a browser with certain default security options disabled (especially these made at compile time using toolchain). Binary exploitation is hard, and extremely not worth the effort in this case.
Ungoogled-chromium is a good substitute in that case
Haven’t used Ungoogled Chromium in a couple years, but I’ve seen some criticisms of it even compared to regular Chrome: https://qua3k.github.io/ungoogled/
Thank you for sharing this, I was unaware. I wonder if any of this has been addressed recently as the linked article is two years old (not demeaning its value, just wondering if the devs saw the article and decided to improve ungoogled-chromium).
Yeah, that’s why I pointed out that I haven’t used it in a couple years, I have no idea about the direction development took after that, so maybe some folks that work on the development of Chromium and its many forks can give us some insight. Personally, I just decided to stick to Firefox tweaked with Arkenfox as my main browser on desktop and I have Brave with all its annoyances turned off as a backup option
They still disable CRLSets and have binaries built by “contributors” not in an automated fashion by the developer themselves.
No one is going to develop exploits only for a browser with certain default security options disabled (especially these made at compile time using toolchain). Binary exploitation is hard, and extremely not worth the effort in this case.
Disabling CRLSets though is worrisome, and its binaries are built by potentially unknown third parties with compromised systems.