unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaelyn <kaelyn.alexi@protonmail.com>
To: Reza Housseini <reza.housseini@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: xz backdoor
Date: Mon, 01 Apr 2024 20:39:48 +0000	[thread overview]
Message-ID: <bu-ZEAFzXy5phdfqULHFUEOyyvkDuBfboNF-Nti29l2J2Ic2-G4wp30XzgLa01IdiVcUJiX9KWquxGRrvmijAMXTSByegdWYfftr4hqEEJs=@protonmail.com> (raw)
In-Reply-To: <3ae39210-ba8b-49df-0ea1-c520011b7cf3@gmail.com>

Hi Reza,

On Monday, April 1st, 2024 at 12:46 PM, Reza Housseini <reza.housseini@gmail.com> wrote:

> 
> 
> Hi Guixers
> 
> Just stumbled upon this recently discovered supply chain attack on xz,
> inserting a backdoor via test files [1, 2]. And it made me wondering,
> what would have been the effects on guix and how can we potentially
> avoid it?

Thank you for your email about the xz backdoor! To hopefully help with your questions, there has already been some discussion on guix-devel about the backdoor and how it should be handled now and in the future:

https://lists.gnu.org/archive/html/guix-devel/2024-03/msg00281.html
https://lists.gnu.org/archive/html/guix-devel/2024-03/msg00292.html

The quick summary is that Guix currently shouldn't be affected because a) Guix currently packages xz 5.2.8, which predates the backdoor, and b) the backdoor includes checks based on absolute paths e.g. under /usr and Guix executable paths generally don't match the patterns checked for.

Cheers,
Kaelyn

> Stay safe!
> Reza
> 
> [1] https://www.openwall.com/lists/oss-security/2024/03/29/4
> [2] https://access.redhat.com/security/cve/cve-2024-3094#cve-cvss-v3


  reply	other threads:[~2024-04-01 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 19:46 xz backdoor Reza Housseini
2024-04-01 20:39 ` Kaelyn [this message]
2024-04-01 20:52   ` Attila Lendvai
2024-04-01 20:44 ` jbranso
2024-04-01 23:27 ` Leo Famulari
2024-04-02  8:23   ` Attila Lendvai
2024-04-02  8:29     ` adanskana
2024-04-02 22:35     ` Ryan Prior

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='bu-ZEAFzXy5phdfqULHFUEOyyvkDuBfboNF-Nti29l2J2Ic2-G4wp30XzgLa01IdiVcUJiX9KWquxGRrvmijAMXTSByegdWYfftr4hqEEJs=@protonmail.com' \
    --to=kaelyn.alexi@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=reza.housseini@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).