From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Reinstatement of zstd and lzma as Global USE flags?
Date: Tue, 12 Nov 2024 09:08:39 -0500 [thread overview]
Message-ID: <3b88c341-d8b0-4363-944b-8e32697faeb9@gentoo.org> (raw)
In-Reply-To: <2755748.mvXUDI8C0e@sun>
[-- Attachment #1.1: Type: text/plain, Size: 1819 bytes --]
On 11/12/24 8:56 AM, Peter Böhm wrote:
> Hello everyone,
>
> as far as I remember correctly, both were activated globally and were only
> removed as global settings due to the security vulnerability of zstd. This is
> now history and I would like to ask if we should re-enable both globally?
It actually happened in https://bugs.gentoo.org/928932
The rationale for dropping it from global USE was:
> This default doesn't actually solve the stated problem, and setting
> it in a high-level profile causes new ones for users who want it
> disabled. The obvious solution to revert to the status quo is to set
> USE="-lzma", but that has the dangerous side-effect of overriding
> IUSE defaults in packages where they are important. For example, sys-
> apps/kmod uses +lzma to ensure that your kernel will boot if you
> choose lzma compression for modules; helpful, because there's no
> other way for the package manager to track that dependency.
And the mailing list discussion involved was:
https://public-inbox.gentoo.org/gentoo-dev/98d180b6db191830e9700d0f5b874274a3fd4755.camel@gentoo.org/
Admittedly, some comments were made at the time that it was "interesting
timing because of the xz backdoor" but the core point made by Michael is
useful to note here:
> What I am saying is that I want the freedom to not have things
> pointlessly enabled on my systems, because similar problems (and worse)
> happen all day every day. The less exposure I have, the better. The
> liblzma backdoor was timely because it will prevent most people from
> telling me I'm being paranoid, but it could have been USE=anything on
> any other day. Moving the defaults out of the high-level profiles will
> give control back to the user, hence my complaint about it.
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2024-11-12 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 13:56 [gentoo-dev] [RFC] Reinstatement of zstd and lzma as Global USE flags? Peter Böhm
2024-11-12 14:08 ` Eli Schwartz [this message]
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=3b88c341-d8b0-4363-944b-8e32697faeb9@gentoo.org \
--to=eschwartz@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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