this post was submitted on 02 Apr 2024
1062 points (95.9% liked)
Programming
16769 readers
102 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"A failure to plan on your part does not constitute an emergency on my part." -Someone hopefully working on ffmpeg.
Wow now that is a quote I'm going to steal. Wondering if "A failure to understand on your part does not constitute an emergency on my part." has the same punch or is as relevant... anyway, thanks for sharing!
Does that go for the xz vulnerability too? Wasn't it a Microsoft dev who discovered that?
In this case, it's actually Microsofts fault. There is no bug in ffmpeg, Microsoft just didn't properly use it
the xz vulnerability was done through a superflous dependency to systemd, xz was only the library that was abused to use systemd's superflous dependency hell. sshd does not use xz, but systemd does depend on it. sshd does not need systemd, but it was attacked through its library dependency.
we should remove any pointless dependencies that can be found on a system to prevent such attacks in future by reducing dependency based attack vectors to a minimum.
also we should increase the overall level of privilege separation where systemd is a good bad example, just look at the init binary and its capability zoo.
The company who hired "the" systemd developer should IMHO start to really fix these issues !
so please hold your "$they have fixed it" back until the the root cause that made the xz dependency level attack possible in the first place has been really fixed =)
Of course pointing it out was good, but now the root cause should be fixed, not just a random symptom that happened to be the first visible atrack that used this attack vector introduced by systemd.