I wouldn't call "nice find, care to help us fix that?" extremely hostile. It can be frustrating for open source projects that far more people want a pat on the back for the identification of a problem (be it security, performance, documentation, or anything else) than there are people who have the time and inclination to help resolve the issue (or ability and inclination to fund the project so it can more easily find help if needed). The use of LLM based tools apparently making that pat on the back easier to attain is going to exacerbate that problem for a while at least.
replyI don’t deal with ffmpeg or C/asm, but there are certainly some 4gl applications that a random patch may cause more problems than it solves. I imagine many researchers would be in that box.
replyhttps://x.com/ffmpeg/status/2039115531744334180?s=46&t=qCSkw...
replySecurity is the punch line for ffmpeg.
I'm glad to see their sense of humour :-)
reply> Assembly is a human readable version of machine code. It's exactly the same.
replygoddamn, and this is a project that prides itself on having had-written assembly in it
There's certainly assembly that maps directly to the machine language bytes, I assume you are talking about the version of assembly with the high level loop macros
replyIn some circles, High Level Assembly (HLA) is lovingly called "Mainframe Assembly".
replyOh my god! They are so funny and memeable! gets RCE'd
replyIn their defense, the "rewrite it in rust" crowd can be really grating.
replyApr Fools Day really is the shittiest day to be online. For one thing, practical jokes/pranks are just gussied-up asshole behavior. For another thing, nerds generally SUCK at information-delivery pranks, which is what the Internet is full of on Apr 1.
replyBack in 2004 when free email services like hotmail were limited to 10-15mb, on April 1st the evening standard front page headline, which I saw in the office around 2pm, was something “Google lunched 1gb email”
replyI couldn’t believe they had fallen for an April fools so hard.
The guy running the twitter account is incompetent but the actual devs are a lot saner I think.
replyI agree it reflects poorly on them though
deleted
reply> … hostile to security researchers who report these issues.
replyDo you have an example?
I don't have an example, but I know the pattern. You are working on your software, security researcher finds a bug, it's in your project, for you it's just another bug, but for them it's a point on their CV, so they make a theater about it, and expect priority in dealing with it. It must get tiring if you get many of these.
replyI've run a bug bounty program for a relatively large corporation and you are exactly right. It's worse in open source, because none of the developers owe a researcher their time. At least in a bug bounty program you've communicated willingness both ways already
replyI have numerous examples of security researchers being hostile and impossible to work with (but cannot share them unfortunately).
replyOne dude running an X account is not indicative of a community to be honest.
replyThat said, that dude has a point. "Researchers" chasing clout with their names attached to CVEs is kind of ridiculous. Half these CVEs are missing bounds checks that can be fixed with a patch in as much effort as writing up the blog post announcing that there was a missing bounds check.
I guess that the perceived problem from a security perspective is that they're there, not that they're necessarily hard to fix once found.
replyThe main beef is the noise created around these disclosures instead of sending patches to fix the bugs.
reply