Sujet : Re: Malware find in the news: xz related.
De : rich (at) *nospam* example.invalid (Rich)
Groupes : comp.os.linux.miscDate : 31. Mar 2024, 18:38:32
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <uuc72o$1ts1m$1@dont-email.me>
References : 1 2 3 4
User-Agent : tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
David W. Hodgins <
dwhodgins@nomail.afraid.org> wrote:
On Sun, 31 Mar 2024 12:05:58 -0400, Grant Taylor <gtaylor@tnetconsulting.net> wrote:
On 3/31/24 08:38, John McCue wrote:
Thanks, here is another interesting link that describes how the issue
occurred and indicates why *BSD and Distros like Slackware would not
be vulnerable.
>
My understanding is that effectively the differentiating factor of if a
distro is impacted or not is if it uses systemd or not.
sshd supports compression. xz is an option for how things are compressed.
ssh supports zlib compression. It (ssh) does not offer lzma/xz as a
compression option.
xz got pulled into ssh on systemd systems because systemd supports
using xz/lzma for journald compression, and it is therefore a
dependency of libsystemd. Some distros patch sshd to link to
libsystemd so that their sshd can "notify" systemd that it is up via a
call to a libsystemd function.