Ungoogled Chromium

[WhiteMoose]

@Cyber-Typhoon

Same way that you ignored that there are CVE notes in the 142.0.7444.134-440598 but there are no CVE notes in the most recent releases but you decided to push that I should be informed since you published things in platforms like Bluesky.

So, if I’m understanding this correctly, the reason you said:

@Cyber-Typhoon

Not sure if I’m understanding how this works, which it probably the case but it seems that Trivalent may be failing on its own propaganda.

is because you combined the AI slop explanation:

@Cyber-Typhoon

Ungoogled Chromium is a Binary Rehoster/Configurator: Its maintainers do not maintain deep custom security patches in the way Trivalent does. Their job is to pull the official Chromium binary/source files, apply their specific ungoogling configuration and scripts, and repackage it.

with the inconsistency in noting fixed CVEs in the Github releases, and just assumed they were removing some CVE fixes because they were too hard to merge with the “deep custom security patches”? If that is not what happened, then I have no idea why you would assume that they don’t have the same CVE patches as other forks based on the same version of chromium.

To tie it back to UC, that project is much more likely to inadvertently do what you assumed Trivalent did, since instead of source code changes being entirely comprised of git diffs that will generate visible merge conflicts when relevant, they have scripts that edit source code as well. This could lead to unnoticed conflicts, including those involving CVE fixes.