Re:FFmpeg Dealing with a Security Researcher
by galaxy_gas on Saturday November 01, 2025 @07:50PM
(#45786595)
The one nice thing is Google had submit a real bug at least.
The human idiot "researchers" will send paragraph long automatically generated extortion threats over not sending HSTS header
Re:FFmpeg Dealing with a Security Researcher
by socalgal2 on Saturday November 01, 2025 @07:14PM
(#45786362)
Because not disclosing an actual bug that could affect users would somehow be good?
Re:FFmpeg Dealing with a Security Researcher
by anon_oss on Sunday November 02, 2025 @07:30AM
(#45789836)
Sorry, I just needed to vent. I see now that Google's AI bug report isn't as bad as I'd assumed.
They should have included a patch though and they should have contacted ffmpeg team first before spamming them with dozens of issues all at once.
Re:FFmpeg Dealing with a Security Researcher
by jsnell on Saturday November 01, 2025 @09:52PM
(#45787220)
So, this is the report they complained about: https://issuetracker.google.com/issues/440183164
I don't know how a vulnerability report could be much better than that. It is a real vulnerability. The report includes a detailed analysis of where the vulnerability is. The bug has been validated, and the report includes exact reproduction instructions.
How is that a bullshit bug report?
But now Google using the full power of their AI to do the same? Fuck off.
"Don't be evil" is long dead and buried. These worthless corporations taking and taking and rarely giving back, and even if they do it's poisoned.