technology

23271 readers

123 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.

founded 4 years ago

MODERATORS

[email protected]

All Linux users, check your XZ library. You might be infected. (www.cyberkendra.com)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

30 comments fedilink hide all child comments

If you're running version 5.6.0 or 5.6.1, downgrade immediately.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 10 points 7 months ago* (last edited 7 months ago)

So the backdoor was not in the source code but in the system used to build the code. Devs for a long time now have swapped over to an automated build system and what happened with this one is in the last step for the xz build process it adds the backdoor to it. You simply have to remove the references to the data in the build config.

EDIT: Rewrote a sentence that sounded stupid