As seen by the infamous FFMPEG incident: https://thenewstack.io/ffmpeg-to-google-fund-us-or-stop-send...
In fact, the article cites one of the FFMPEG maintainers as being grateful for the vulnerability reports.
Did I miss something?
Google is extorting benefit, specifically fixes to software it heavily depends on for its multi billion dollar business, by coercion, specifically by actively threatening the project with reputational damage in 90 days if certain action is not taken, even if the action is not in the vendors best interest.
As a thought experiment, imagine if Google was reporting this to the project, but _without_ the 90 day limit. The one that the original article describes going down to 60 then 30 days. Yes, you might first think "that will cause the projects to never fix bugs" which might be true for some projects, but you do realize how legally that would completely change the dynamic between Google and the project and remove the entire extortion part from the picture? Or indeed, if they simply published it without any notice at all.
Whether or not other people also happen to benefit is related, but it doesn't remove the fact that Google also benefits.
Or if you would like a more vivid picture:
If the Mob forces you to give them a room in your hotel for illegal poker tournaments and then gives you tips on how to make the windows safer so that bricks can't fly through them, it does improve safety for all your clients but it's still extortion.
I would prefer ffmpeg team to have the time to focus on slightly newer stuff, as a user myself.
Just because the response can be "No", it doesn't mean Google didn't require _something_ from ffmpeg.
If they wanted to, they could also have "close to bug when fixed and we will only then notify the public", or they could have 0-day and just publish without notice.
But because they _actively choose_ 90 (60, 30) day windows, they _do_ require something from the projects that they report on.
It requires zero things from ffmpeg. As it is today, they privately contact them with info about the vulnerability and also informs them that in 90 days the whole world will know about the vulnerability too.
ffmpeg ca either fix it if it wants or be "cool story bro, yolo".
Why would a project get to tell somebody who found a vuln when they can talk about it to the public?
Imagine you go to a restaurant and see an issue with the food. You tell the restaurant “hey I’m writing a review of this. I’m going to publish it in a month; if you want to include any response before that time I’ll include it in my review”.
It would be nuts for the restaurant to say “actually we require you wait 180 days to publish”.
You can also take a look at how essentially all investigative reporting works, where a reporter asks the subject for comment before publishing.
Famously, leaving reviews on TripAdvisor in Germany can get you sued.
I did some light searching here and the examples appear to match what I’d expect: you can be liable if you lie about facts, but if you’re sharing your opinions or accurately relating what happened, you’re fine.
Can you provide some examples for your claim?
Similarly, if there were a jurisdiction somewhere in the world where vulnerability research was criminalized I don't think that would be relevant to the conversation we're having here. AFAIK project zero is subject only to US law.
If they provided evidence of their claim, I would have learned something new and it would be potentially interesting to the discussion about the risks of making public factual disclosures in places other than the US. It’s not a matter of whether or not it would be something to celebrate.
Countries attempt, with varying levels of success, to regulate international entities based on activity they conduct elsewhere in the world all the time.
And as an aside, it’s not clear that Project Zero is actually purely US-based: https://www.google.com/about/careers/applications/jobs/resul...
What do you think Google is extorting from the publishers of insecure software - reduced security vulnerabilities? Or what is it that you think Google is actually after by doing this?
> guise of security
What do you think is the real motivation if not security?