News for hackers. Stuff that matters.
Re:Backdoor in upstream xz/liblzma leading to SSH server com... by fragmede on Friday March 29, 2024 @06:38PM (#39869785)
seems trivial for a configure script to call curl/wget somewhere in the depths of it, no?
Re:Backdoor in upstream xz/liblzma leading to SSH server com... by timschmidt on Friday March 29, 2024 @06:52PM (#39869889)
Exactly. And at least Cargo will refuse to download a crate which has been yanked. So any crate which has been discovered to be compromised can be yanked, preventing further damage even when someone has already downloaded something which depends on it.

Building packages with up-to-date dependencies is also vastly preferable to building against ancient copies of libraries vendored into a codebase at some point in the past, a situation I see far too often in C/C++ codebases.

Re:Backdoor in upstream xz/liblzma leading to SSH server com... by Hackbraten on Friday March 29, 2024 @08:41PM (#39870654)
Debian’s rules files often deliberately sinkhole the entire network during the build. It’s not the worst idea.
Re:Backdoor in upstream xz/liblzma leading to SSH server com... by fragmede on Saturday March 30, 2024 @08:26AM (#39874178)
I wonder if you could do it inside the config script without the network.