this post was submitted on 04 Feb 2026
475 points (99.6% liked)

Programming

25249 readers
741 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

It's hard to imagine something as fundamental to computing as the sudo command becoming abandonware, yet here we are: its solitary maintainer is asking for help to keep the project alive.

Archived version

you are viewing a single comment's thread
view the rest of the comments
[–] Scrollone@feddit.it 26 points 21 hours ago (1 children)

To be honest, it wouldn't take much for distro maintainers to detect that and stop it

[–] JustEnoughDucks@feddit.nl 4 points 12 hours ago (1 children)

But who is seriously looking at the sudo code at every update. I would bet a lot of money that the vast majority simply trust him and gloss over it maximum.

The chain of trust has to exist otherwise distrobox maintainers would spend 24 hours a day reviewing code changes and only update once every 6 months.

[–] cows_are_underrated@feddit.org 10 points 10 hours ago (2 children)

You may want to look into how the xz backdoor has been discovered. That backdoor was very well hidden. Implementing a crypto mining malware would be blatantly obvious and yes, people do in fact look at such code

[–] bradboimler@lemmy.world 2 points 2 hours ago

That was scary. I had the bad version on my computer for a bit.

[–] JustEnoughDucks@feddit.nl 4 points 3 hours ago

Yes, but people are forgetting how it was discovered.

It was discovered because there was a visible performance impact by running benchmark tests on other, time-critical software.

Do you know how it was not discovered? By maintainers looking through changes of the software and looking through the code, exactly the way that the commenter and you and others are saying things would be caught.

If the attacker hadn't been so eager and only set it to start working after a time delay a year later or multiple updates later? It would have infected almost every server in the world, even if it got noticed immediately, it would have been a giant problem that would have reaped the benefits for the malicious party before it could be regressed and changed.