this post was submitted on 30 Mar 2024
474 points (84.4% liked)

linuxmemes

21197 readers
283 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] lemmyvore@feddit.nl 91 points 7 months ago (4 children)

    I thought Arch was the only rolling distro that doesn't have the backdoor. Its sshd is not linked with liblzma, and even if it were, they compile xz directly from git so they wouldn't have gotten the backdoor anyway.

    [–] angel@iusearchlinux.fyi 30 points 7 months ago

    TBF they only switched to building from git after they were notified of the backdoor yesterday. Prior to that, the source tarball was used.

    [–] qwioeue@lemmy.world 21 points 7 months ago* (last edited 7 months ago) (1 children)

    liblzma is the problem. sshd is just the first thing they found that it is attacking. liblzma is used by firefox and many other critical packages.

    [–] Rustmilian@lemmy.world 32 points 7 months ago (2 children)

    Arch does not directly link openssh to liblzma, and thus this attack vector is not possible. You can confirm this by issuing the following command:

    ldd "$(command -v sshd)"
    
    [–] qwioeue@lemmy.world 7 points 7 months ago* (last edited 7 months ago) (4 children)

    Yes, this sshd attack vector isn't possible. However, they haven't decomposed the exploit and we don't know the extent of the attack. The reporter of the issue just scratched the surface. If you are using Arch, you should run pacman right now to downgrade.

    [–] Fubarberry@sopuli.xyz 36 points 7 months ago

    They actually have an upgrade fix for it, at least for the known parts of it. Doing a standard system upgrade will replace the xz package with one with the known backdoor removed.

    [–] HopFlop@discuss.tchncs.de 15 points 7 months ago

    If you are using Arch, you should run pacman right now to downgrade.

    No, just update. It's already fixed. Thats the point of rolling release.

    [–] Trail@lemmy.world 4 points 7 months ago

    Bold of you to assume I hare upgraded in the first place.

    [–] lemmyvore@feddit.nl 3 points 7 months ago

    I switched it with 5.4, just in case.

    [–] bitwolf@lemmy.one 0 points 7 months ago

    Do not use ldd on untrusted binaries.

    I executed the backdoor the other day when assessing the damage.

    objdump is the better tool to use in this case.

    [–] qupada@kbin.social 11 points 7 months ago* (last edited 7 months ago)

    Interestingly, looking at Gentoo's package, they have both the github and tukaani.org URLs listed:

    https://github.com/gentoo/gentoo/blob/master/app-arch/xz-utils/xz-utils-5.6.1.ebuild#L28

    From what I understand, those wouldn't be the same tarball, and might have thrown an error.

    [–] possiblylinux127@lemmy.zip 3 points 7 months ago

    The extent of the exploit is still being analyzed so I would update and keep your eye on the news. If you don't need your computer you could always power down.