Navigate Select ESC Close

What Everyone Missed About The Linux Hack

2024-04-01 Science & Technology
294.9k
13.6k
1.3k
Theo - t3․gg
Theo - t3․gg
539.0k subscribers

Unlock all features

FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.

Description

The xz exploit pushed the limits of social engineering, code obfuscation, package distribution and more. I'm concerned the important parts aren't being covered, so I decided to do a vid FOLLOW LOW LEVEL: @LowLevelTV This blog post carried the video: https://robmensching.com/blog/posts/2024/03/30/a-microcosm-of-the-interactions-in-open-source-projects/ Follow Rob as well: https://twitter.com/robmen Maintainer's blog post: https://tukaani.org/xz-backdoor/ Diagram: https://twitter.com/fr0gger_/status/1774342248437813525 S/O Ph4se0n3 for the awesome edit 🙏

Top Comments (10)

@meschine 2024-04-01

Thanks for highlighting this topic, Theo. We need to do more to support OSS maintainers. I share your feelings of anger and horror for this maintainer: Lasse Collin. While writing my thoughts down, I tried to hard to keep _most_ of the anger out of the text but my keyboard suffered. This is a particularly scary situation but I worry because its not uncommon. It needs to change.

1.5k 27 replies
@Lucas-gt8en 2024-04-01

Dude this poor original maintainer. Even when you somehow ignore the chaos and felt responsibility there’s also the fact that somebody that he trusted lied about probably pretty much everything. I’d be genuinely surprised if this was not orchestrated by a state agency of a major country (US, Russia, China, Western EU) but I doubt we’ll ever find out

473 20 replies
@DarylMetzler 2024-04-01

This attack hit the entire software exploit playbook. Built trust? Check. Socially engineered a situation? Check. Built an elaborate, difficult to detect exploit? Check. Managed to infiltrate a wide scope of possible downstream systems? CHECK! I hope there is recourse against this (these?!) bad actor(s).

770 24 replies
@planetmarshalluk 2024-04-02

Really interesting video, I do think that the developer who discovered the exploit should be given a bit more respect than just "some random guy at Microsoft". They clearly went to a lot of effort and care about the quality of their work.

613 16 replies
@FabianLopez_lomba 2024-04-02

Imagine finding this exploit only to be called "a random Microsoft engineer"

1.6k 43 replies
@embedyt 2024-04-01

this xz stuff is honestly so interesting, crazy that some guy at microsoft only found it cause he happened to be benchmarking and noticed a 500ms difference in ssh login speed. if he never noticed we'd probably not know about this until it was way too late.

723 17 replies
@Ewan_Valentine 2024-04-01

That maintainer needs the worlds biggest hug, support and love from everyone in our industry

414 13 replies
@bobbybyrne1899 2024-04-02

If you work in a company, advocate for time and/or money be put towards the foss tools and libraries the company uses frequently. It's how the open source model is supposed to work. It's also a PR gold mine to show how your company is contributing back in meaningful ways. Helps attract talent as well.

27
@CFSworks 2024-04-02

I fully agree that it's unacceptable to be blaming Lasse or how the XZ Utils project has been run, and even from day one I was not seeing any significant deviation from the standard operating procedure. He was doing everything "the right way." But, human nature being what it is, most people are in denial of the fact that the FOSS ecosystem *itself* is what's vulnerable/targeted here, and they're desperate to fault XZ/Lasse for the attack to maintain that denial: "He screwed up by accepting weird PRs." (He did not, Jia was given full committer access.) "He screwed up by letting the code get overly complex enough for the backdoor's entry point to hide in plain sight." (It wasn't in plain sight, Jia added it manually to the release tarballs.) "The project shouldn't have been releasing curated tarballs, those should come from git-archive automatically." (Perhaps, but this was standard practice, not individual sloppiness.) Don't get me wrong, I think we're going to learn some valuable ways to change the "standard operating procedure" of FOSS to make it more resilient against this kind of thing even in the face of a burned-out maintainer and malicious co-maintainer, but we NEED to have these discussions in the context of the status quo not being good enough, rather than Lasse being not good enough to follow the status quo.

144 7 replies
@CodingGimmic 2024-04-01

Social Engineering hack was Kevin Mitnick's #1 skill when he was wanted and still alive.

140 4 replies

Unlock the Data Inside
Turn Videos into Knowledge

  • Get FREE 10/day: transcripts, summaries, chats
  • Chat with videos, export text & PDF
  • $1 free API credit for RAG, chatbots & research

Free forever plan • All features unlocked

App screenshot