From: uuuvn <uuuvn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: ungoogled-chromium
Date: Fri, 25 Mar 2022 18:03:24 +0100 [thread overview]
Message-ID: <20220325170324.xz4iRFj_8sKj2QB8hxxrWYfmjk9efJq9fu06RBf7OWQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-10664@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
New comment by uuuvn on void-packages repository
https://github.com/void-linux/void-packages/issues/10664#issuecomment-1079223633
Comment:
> Let's not, it always lags at least one major version behind upstream Chromium (which we already do way too often), which tends to have some not so nice CVEs. IMHO use FF instead if you don't want to deal with Google
Now ugc is practically on par with upstream.
Regarding security risks: https://madaidans-insecurities.github.io/firefox-chromium.html . TL;DR Firefox is one big hole, even chromium with known 1-day vulnerability without PoC is safer IMHO.
Regarding the fear of google:
- https://digdeeper.neocities.org/ghost/mozilla.html (tl;dr mozilla is a controlled opposition that does everything the same as google, but pretends to care about privacy)
- https://spyware.neocities.org/articles/firefox.html (about the amount of spyware in firefox)
- https://codeberg.org/shadow/SpywareWatchdog/issues/58 (firefox mitigation guide is deprecated)
For me personally, the lack of ungoogled chromium in the official repositories and distrust of third-party ones is a big headache when using voidlinux right now, I think I'm not the only one.
next parent reply other threads:[~2022-03-25 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-10664@inbox.vuxu.org>
2022-03-25 17:03 ` uuuvn [this message]
2022-03-25 17:07 ` uuuvn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220325170324.xz4iRFj_8sKj2QB8hxxrWYfmjk9efJq9fu06RBf7OWQ@z \
--to=uuuvn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).