misinfo, rustlang
Rust 2024 edition is about to drop! Here are some of the new features they’re adding to the standard library:
I accidentally found a security issue while benchmarking postgres changes.
If you run debian testing, unstable or some other more "bleeding edge" distribution, I strongly recommend upgrading ASAP.
Whenever you feel like saying "dude", just say "gamer".
"Gamer" is....
1) Gender neutral: Everyone can be a gamer
2) Guaranteed to piss somebody off because not everybody identifies as "gamer", but they can't give you any real flak for it because see point number one.
@eb I really hope that this causes an industry-wide reckoning with the common practice of letting your entire goddamn product rest on the shoulders of one overworked person having a slow mental health crisis without financially or operationally supporting them whatsoever. I want everyone who has an open source dependency to read this message https://www.mail-archive.com/xz-devel@tukaani.org/msg00567.html
I’ve seen numerous people express concern that their xz installation is several versions out of date — because while it may have saved them in this specific case, doesn’t that mean they must not be running updates correctly in general?
No! It’s normal for your personal copy of an open source program to be several versions out of date. When you get an update to a commercial software package, it’s already been through months of internal testing by professionals. In volunteer-based open source, the bulk of this testing is done by simply releasing the update on their site and letting advanced users try it out. At some point, if there’s no problems, it will get shuffled forward to stable update channels. Therefore it’s normal for most Linux software to be one to two years out of date compared to the absolute newest version you could possibly get.
The good news is that this backdoor was found before most distros accepted the update as stable, and therefore it was not yet installed on the majority of production servers — it’ll be mainly on testing servers. The bad news is that the malicious actor was clever enough to make sock puppet user accounts to complain about xz crashing and claim that the new update is a critical fix that needs to be rushed out the door as soon as possible. This was a close call, we were very lucky.
Me: "Wait, why doesn't Unreal have a cone trace?"
Marketplace: "Don't worry friend, we gotcha, check out this plugin"
<looks>
Me: "This only raises further questions"
Terry keeps rolling out the bangers. Finally, he's found his medium.
2913. Periodic Table Regions
title text: Cesium-133, let it be. Cesium-134, let it be even more.
(https://xkcd.com/2913)
(https://www.explainxkcd.com/wiki/index.php/2913)
A couple things to think about here:
This appears to be a malicious maintainer - not a compromised account. Meaning the person themselves, coded this in an pushed it out.
So:
1) Did they try and backdoor any other code?
2) Are they part of a greater campaign or is anyone else helping them.
This is a massive breach of trust.
That said! Huge kudos to Andres Freund, Florian Weimer, and others in finding this.
A lot of eyes are on this now. CISA is involved. Major distros are involved, etc. Many eyes and such.
xz-utils was backdoored by its upstream. Tracked as CVE-2024-3094 and thoroughly documented by vuln discoverer Andres Freund on oss-security@: https://www.openwall.com/lists/oss-security/2024/03/29/4
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess