From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Toon Moene <toon@moene.org>
Cc: Ian Lance Taylor <iant@golang.org>, gcc@gcc.gnu.org
Subject: Re: Sourceware mitigating and preventing the next xz-backdoor
Date: Wed, 3 Apr 2024 19:51:17 +0100 [thread overview]
Message-ID: <CAH6eHdSL3ApfwMDcJ9A29eekWn1gYA3JeWLPU-ox+QfK1zT3fw@mail.gmail.com> (raw)
In-Reply-To: <e2e115d0-889d-42fa-a255-cc0b6e53401f@moene.org>
On Wed, 3 Apr 2024 at 19:36, Toon Moene <toon@moene.org> wrote:
>
> On 4/3/24 20:25, Ian Lance Taylor wrote:
>
> > Note that the attack really didn't have anything to do with
> > compressing data. The library used an IFUNC to change the PLT of a
> > different function, so it effectively took control of the code that
> > verified the cryptographic key. The only part of the attack that
> > involved compression was the fact that it happened to live in a
> > compression library. And it wouldn't matter whether the code that
> > verified the cryptographic key was run as root either; the effect of
> > the attack was to say that the key was OK, and that sshd should
> > execute the command, and of course that execution must be done on
> > behalf of the requesting user, which (as I understand it) could be
> > root.
>
> Ah, OK - that's what I missed.
>
> Does your explanation mean that - if, as I do in my sshd config file -
> you *forbid* root access via sshd in *any* way, you wouldn't be vulnerable ?
No, sshd is still running as root.
next prev parent reply other threads:[~2024-04-03 18:51 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 20:39 Security warning about xz library compromise Mark Wielaard
2024-04-01 15:06 ` Sourceware mitigating and preventing the next xz-backdoor Mark Wielaard
2024-04-02 19:54 ` Sandra Loosemore
2024-04-02 20:03 ` Paul Eggert
2024-04-02 20:20 ` Paul Koning
2024-04-02 20:28 ` Ian Lance Taylor
2024-04-03 6:26 ` Martin Uecker
2024-04-03 14:00 ` Michael Matz
2024-04-03 14:14 ` Paul Koning
2024-04-03 14:32 ` Martin Uecker
2024-04-03 14:46 ` Jeffrey Walton
2024-04-03 16:02 ` Michael Matz
2024-04-03 16:26 ` Joel Sherrill
2024-04-03 16:32 ` Martin Uecker
2024-04-03 16:51 ` Andreas Schwab
2024-04-03 16:56 ` Jonathan Wakely
2024-04-03 17:38 ` Paul Floyd
2024-04-03 18:50 ` Andreas Schwab
2024-04-03 18:46 ` Jonathon Anderson
2024-04-03 19:01 ` Martin Uecker
2024-04-05 21:15 ` Andrew Sutton
2024-04-06 13:00 ` Richard Biener
2024-04-06 15:59 ` Martin Uecker
2024-04-04 13:59 ` Michael Matz
2024-04-09 16:44 ` anderson.jonathonm
2024-04-09 17:57 ` Andreas Schwab
2024-04-09 19:59 ` Jonathon Anderson
2024-04-09 20:11 ` Paul Koning
2024-04-09 21:40 ` Jeffrey Walton
2024-04-09 21:50 ` Paul Eggert
2024-04-09 21:58 ` Sam James
2024-04-09 22:15 ` Paul Eggert
2024-04-09 22:22 ` Sam James
2024-04-09 22:53 ` Paul Eggert
2024-04-09 22:03 ` Jonathon Anderson
2024-04-09 22:10 ` Sam James
2024-04-09 21:54 ` Jonathon Anderson
2024-04-09 22:00 ` Sam James
2024-04-10 14:09 ` Frank Ch. Eigler
2024-04-10 18:47 ` Jonathon Anderson
2024-04-10 19:00 ` Frank Ch. Eigler
2024-04-10 10:26 ` Claudio Bantaloukas
2024-04-24 8:32 ` Boris Kolpackov
2024-04-24 9:16 ` Andreas Schwab
2024-04-02 22:08 ` Guinevere Larsen
2024-04-02 22:50 ` Jeffrey Walton
2024-04-02 23:20 ` Mark Wielaard
2024-04-02 23:34 ` Paul Koning
2024-04-03 0:37 ` Jeffrey Walton
2024-04-03 8:08 ` Florian Weimer
2024-04-03 13:53 ` Joel Sherrill
2024-04-04 10:25 ` Mark Wielaard
2024-04-10 16:30 ` Alejandro Colomar
2024-04-21 15:30 ` Mark Wielaard
2024-04-21 20:40 ` Alejandro Colomar
2024-04-21 20:52 ` Alejandro Colomar
2024-04-30 11:28 ` Alejandro Colomar
2024-04-03 14:04 ` Tom Tromey
2024-04-03 14:42 ` Jeff Law
2024-04-04 10:48 ` Mark Wielaard
2024-04-03 18:04 ` Toon Moene
2024-04-03 18:24 ` Paul Koning
2024-04-03 18:25 ` Ian Lance Taylor
2024-04-03 18:36 ` Toon Moene
2024-04-03 18:51 ` Jonathan Wakely [this message]
2024-04-09 21:02 ` James K. Lowden
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=CAH6eHdSL3ApfwMDcJ9A29eekWn1gYA3JeWLPU-ox+QfK1zT3fw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@golang.org \
--cc=toon@moene.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 read-only IMAP folder(s) and NNTP newsgroup(s).