From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [gentoo-dev] Current unavoidable use of xz utils in Gentoo
Date: Sun, 31 Mar 2024 08:39:14 -0700 [thread overview]
Message-ID: <422183bb-1fcc-47b0-a729-2a360feab38d@gmail.com> (raw)
In-Reply-To: <2676120.BddDVKsqQX@rogueboard>
On 3/31/24 07:59, Michael wrote:
> On Sunday, 31 March 2024 13:33:20 BST Rich Freeman wrote:
>> (moving this to gentoo-user as this is really getting off-topic for -dev)
>
> Thanks for bringing this to our attention Rich.
>
> Is downgrading to app-arch/xz-utils-5.4.2 all that is needed for now, or are
> we meant to rebuilding any other/all packages, especially if we rebuilt our
> @world only a week ago as part of the move to profile 23.0?
I just ran `glsa-check -l affected` and it came up blank for me.
I ran `emerge --sync` and checked again and it indeed says my machine is
affected.
I then ran `emerge -auDN world` and it automatically downgraded.
So, all we need to do sync and update world. It will downgrade xz-utils
automatically.
If you want to make sure, run `glsa-check -l affected` after the emerge
world, if it comes up blank you are not affected. Or run `glsa-check -l
202403-02` and it will tell you if you are affected:
$ glsa-check -l 202403-04
[A] means this GLSA was marked as applied (injected),
[U] means the system is not affected and
[N] indicates that the system might be affected.
202403-04 [U] XZ utils: Backdoor in release tarballs ( app-arch/xz-utils )
Dan
next prev parent reply other threads:[~2024-03-31 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a2e3bb067a078bffaa860bdf5e11977d.squirrel@ukinbox.ecrypt.net>
[not found] ` <bea7dbcb-8659-43fe-b90c-e8d8b93c52ce@gmail.com>
[not found] ` <f41893920d7bd6dde5ae8665c4603b63@shitposting.expert>
2024-03-31 12:33 ` [gentoo-user] Re: [gentoo-dev] Current unavoidable use of xz utils in Gentoo Rich Freeman
2024-03-31 14:59 ` Michael
2024-03-31 15:39 ` Daniel Frey [this message]
2024-03-31 16:04 ` Rich Freeman
2024-03-31 22:19 ` Michael Orlitzky
2024-03-31 22:29 ` Michael Orlitzky
2024-03-31 22:32 ` Alexandru N. Barloiu
2024-03-31 22:36 ` Michael Orlitzky
2024-03-31 22:41 ` Alexandru N. Barloiu
2024-03-31 19:38 ` Håkon Alstadheim
2024-03-31 21:36 ` Wol
2024-03-31 21:52 ` Rich Freeman
2024-04-15 13:08 ` Frank Steinmetzger
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=422183bb-1fcc-47b0-a729-2a360feab38d@gmail.com \
--to=djqfrey@gmail.com \
--cc=gentoo-user@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