Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #10176

S

segmentation fault

Personal blog · qua3k.github.iosecurityprogramming

segmentation fault is a personal blog at qua3k.github.io about security and programming. Since 2021, 8 different Hacker News readers have linked it 9 times, most often “A review of Ungoogled-Chromium patches”. The last post was in 2022, but the archive is still widely read.

Visit the blog
9mentions?
8HN people?
2021–2025first – last linked?
Links on Hacker News per year · peak 3 in 2023

Too few sampled comments (7) to say how often HN recommends it.?

Why HN links it

HN readers cite this blog's ungoogled-chromium page as a reference on its security drawbacks, including lagging updates, disabled out-of-band security updates, and missing control-flow integrity builds.

Summarised by Claude from a sample of 7 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

hi i'm a duck and these are my ramblings

Most-linked posts?

  1. A review of Ungoogled-Chromium patches
    7 people · 7 mentions · first linked 2021-11-30

What Hacker News says?

  1. From what I've understood, it's not recommended to run Ungoogled Chromium: https://qua3k.github.io/ungoogled-chromium

    Comment linking /ungoogled-chromium

    on “Improving Firefox stability on Linux”
  2. Submitted A review of Ungoogled-Chromium patches as a story · 2 points

    HN discussion
  3. The only problem is it disables OOB security updates. https://qua3k.github.io/ungoogled/

    Comment linking /ungoogled/

    on “Helium Browser”
  4. Submitted Improving Browser Security (2021) as a story · 1 points

    HN discussion
  5. It's worth noting that UGC has some significant security regressions https://qua3k.github.io/ungoogled/

    Comment linking /ungoogled/

    on “Google has added ads on both its search page and Chrome://newtab”
  6. Namely, there's quite a but of lag in updates. I think the reason why that's bad should be apparent. They also don't build with control-flow integrity enabled [0]. They don't enable the is_official_build flag which enables some security features (including CFI), and disables some debug stuff that a regular user shouldn't be using [1]. 0: https://qua3k.github.io/ungoogled/ 1: https://groups.google.com/a/chromium.org/…

    Comment linking /ungoogled/

    on “Google Chromium, sans integration with Google”
  7. > Whats the current consensus on Brave? If you want to use Chromium based browsers it's probably the only browser that is: - Cares about security, (not doing stupid shit like disabling CRLSets), they are proxied by Brave. See https://qua3k.github.io/ungoogled/ - Does try to do some anti-fingerprinting, while its not a strong as Firefox+Arkenfox, it's at least a step in the direction as opposed to other browsers whic…

    Comment linking /ungoogled/

    on “Privacy-Respecting Software”
  8. The author recommends using "Do Not Track", but this has been deprecated for some time. Safari and Firefox have both removed the option completely. Perhaps the author meant GPC? For all of the security suggestions in this article I was also surprised to see the author recommending ungoogle-chromium, which has a number of security issues. See: https://qua3k.github.io/ungoogled/ The primary issue I take with the artic…

    Comment linking /ungoogled/

    on “A Word on Omarchy”
  9. IMO the browser is far too important to use third-party builds containing patches that don't receive serious audit. For example, the Chromium packages provided by the vast majority of Linux distros disable security features like CFI (check your favorite distro's x86_64 Chromium package build log and look for the "is_cfi" argument). I think Arch is the only exception. ungoogled-chromium has similar problems https://q…

    Comment linking /ungoogled/

    on “Google Chrome pushes browser history-based ad targeting”

Search all of HN for qua3k.github.io