pull down to refresh

For years, I've taken it as gospel that VLC was the open source media choice (and taken it to every platform I've used), but after reading these tweets, I'm less certain. That last tweet, in particular, reminds me of the issue we all recognize around using "crypto" wallets instead of dedicated Bitcoin wallets -- why offer up extra attack vectors via things we're not even using?
Going to be taking a deep dive looking into MPV today.
Would appreciate explicit alternatives. I'm not getting my family to use an ffmpeg wrapper from the command line.
reply
MPV (the app she mentions) does have downloadable executables that I'm playing with right now. They seem to do the trick, but it's much more bare-boned. Will be going down the rabbit-hole deeper later this week, though.
reply
My phone won’t load the tweets ahhhhhh
reply
Disagree
Code execution through subtitles is bad. But is being/will be fixed.
If you have compromised files that's on you. Skill issue.
The far greater threat is the fast growing amount of codecs and file formats that have to be supported on a huge number of platforms. In a landscape that is only a few decades old. If you want longevity of your data you have to embrace the big dogs of FOSS. There is no way around it.
reply
I agree with Laurie here. The VLC codebase is a mess. The RCE from subtitles is merely a symptom. Yes, all code has bugs. Some code is buggier than others. The surface area of all those codecs and file parsers really adds up. The fact it was an example of “easy to find vulns” in the past is also telling.
If you look at 0-click exploits for mobile in the last few years, the almost certainly relate to file or content parsing. It’s going to continue to be a thing as long as there is untrusted data being parsed in unsafe languages.
Skill issue! Blame the victim. Oh my. If only it was that simple.
reply
ahh...sheit
reply
reply
@ek would it be possible to include a snapshot here in case the tweet gets deleted?
reply
0 sats \ 0 replies \ @ek 15 Jan
oof
reply