From: Kees Cook <keescook@chromium.org>
To: Lasse Collin <lasse.collin@tukaani.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>, Jia Tan <jiat0218@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [tech-board] [PATCH 00/11] xz: Updates to license, filters, and compression options
Date: Sat, 30 Mar 2024 06:54:30 -0700 [thread overview]
Message-ID: <202403300652.7EAF7B53@keescook> (raw)
In-Reply-To: <20240330144848.102a1e8c@kaneli>
On Sat, Mar 30, 2024 at 02:48:48PM +0200, Lasse Collin wrote:
> On 2024-03-29 Andrew Morton wrote:
> > On Fri, 29 Mar 2024 14:51:41 -0600 Jonathan Corbet <corbet@lwn.net>
> > wrote:
> >
> > > > Andrew (and anyone else), please do not take this code right now.
> > > >
> > > > Until the backdooring of upstream xz[1] is fully understood, we
> > > > should not accept any code from Jia Tan, Lasse Collin, or any
> > > > other folks associated with tukaani.org. It appears the domain,
> > > > or at least credentials associated with Jia Tan, have been used
> > > > to create an obfuscated ssh server backdoor via the xz upstream
> > > > releases since at least 5.6.0. Without extensive analysis, we
> > > > should not take any associated code. It may be worth doing some
> > > > retrospective analysis of past contributions as well...
> > > >
> > > > Lasse, are you able to comment about what is going on here?
> > >
> > > FWIW, it looks like this series has been in linux-next for a few
> > > days. Maybe it needs to come out, for now at least?
> >
> > Yes, I have removed that series.
>
> Thank you. None of these patches are urgent. I'm on a holiday and only
> happened to look at my emails and it seems to be a major mess.
>
> My proper investigation efforts likely start in the first days of
> April. That is, I currently know only a few facts which alone are bad
> enough.
>
> Info will be updated here: https://tukaani.org/xz-backdoor/
Thanks; I appreciate the update! And I'm sorry this has happened to you.
We'll all know more in the coming days. (I, too, am on vacation, wheee.)
-Kees
--
Kees Cook
prev parent reply other threads:[~2024-03-30 13:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 18:38 [PATCH 00/11] xz: Updates to license, filters, and compression options Lasse Collin
2024-03-20 18:38 ` [PATCH 01/11] MAINTAINERS: Add XZ Embedded maintainers Lasse Collin
2024-03-20 18:38 ` [PATCH 02/11] LICENSES: Add 0BSD license text Lasse Collin
2024-03-20 18:38 ` [PATCH 03/11] xz: Switch from public domain to BSD Zero Clause License (0BSD) Lasse Collin
2024-03-20 18:38 ` [PATCH 04/11] xz: Documentation/staging/xz.rst: Revise thoroughly Lasse Collin
2024-03-20 18:38 ` [PATCH 05/11] xz: Fix comments and coding style Lasse Collin
2024-03-20 18:38 ` [PATCH 06/11] xz: Cleanup CRC32 edits from 2018 Lasse Collin
2024-03-20 18:38 ` [PATCH 07/11] xz: Optimize for-loop conditions in the BCJ decoders Lasse Collin
2024-03-20 18:38 ` [PATCH 08/11] xz: Add ARM64 BCJ filter Lasse Collin
2024-03-20 18:38 ` [PATCH 09/11] xz: Add RISC-V " Lasse Collin
2024-03-20 18:38 ` [PATCH 10/11] xz: Use 128 MiB dictionary and force single-threaded mode Lasse Collin
2024-03-20 18:38 ` [PATCH 11/11] xz: Adjust arch-specific options for better kernel compression Lasse Collin
2024-03-31 0:42 ` angel.lkml
2024-04-03 19:59 ` Lasse Collin
2024-04-04 14:01 ` Lasse Collin
2024-03-29 19:24 ` [PATCH 00/11] xz: Updates to license, filters, and compression options Jonathan Bennett
2024-03-29 19:32 ` Kees Cook
2024-03-29 20:51 ` [tech-board] " Jonathan Corbet
2024-03-30 0:37 ` Kees Cook
2024-03-30 2:56 ` [tech-board] " Andrew Morton
2024-03-30 12:48 ` Lasse Collin
2024-03-30 13:54 ` Kees Cook [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=202403300652.7EAF7B53@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jiat0218@gmail.com \
--cc=lasse.collin@tukaani.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.