6 ms·
Fully on FFmpeg team side, many companies approach to FOSS is only doing so when it sounds good on their marketing karma, leech otherwise. Most of them would j
by pjmlp 1y ago
Fully on FFmpeg team side, many companies approach to FOSS is only doing so when it sounds good on their marketing karma, leech otherwise.
Most of them would just pirate in the old days, and most FOSS licences give them clear conscience to behave as always.
- PeaceTed 1y agoThis is why many have warned against things like MIT licence. Yes, it gives you source code and does easily get incorporated into a lot of projects but it comes at the cost of potential abuse. Yes, GPL 3 is a lot ideologically but it was trying to limit excessive leeching. Now that I have opened the flood gates of a 20 year old debate, time to walk away.
- esrauch 1y agoGoogle Project Zero just looks for security issues in popular open source packages, regardless of if Google itself even uses those packages or not. So I'm not sure what GPLv3 really has to do with it in this case, if it under was a "No billion dollar company allowed" non-free-but-source-available license, this same thing would have happened if the project was popular enough for Project Zero to have looked at it for security issues.
- cestith 1y agoThe difference is that Google does use it, though. They use it heavily. All of us in the video industry do - Google, Amazon, Disney, Sony, Viacom, or whoever. Companies you may have never heard of build it into their solutions that are used by big networks and other streaming services, too.
- esrauch 1y agoRight, Google absolutely should fund ffmpeg. But opening security issues here is not related to that in any way. It's an obscure file format Google definitely doesn't use, the security issue is irrelevant to Google's usages of it. The critique would make sense if Google was asking for ffmpeg to implement something that Google wanted, instead of sending a patch. But they don't actually care about this one, they aren't actually asking for them to fix it for their benefit, they are sending a notice of a security issue that only affects people who are not Google to ffmpeg.
- robocat 1y agoGoogle absolutely does fund ffmpeg via SPI. "and Google provided substantial donations to SPI's general fund". The amounts don't appear to be public (and what is enough!?)
- cestith 1y agoOpening a security issue is not the problem. A public disclosure so soon when there are so many machine-assisted reports for such obscure issues is the problem. If Google wants to force a faster turnaround on the fixes, they can send the reports with patches or they can pay for prioritization.
- jsnell 1y agoThree months is "soon"? What do you think is reasonable? And like so many posters in this thread, you seem to be under the impression that Google needed this fixed at some specific timeline. In reality the fix timeline, or even a total lack of a fix, makes no impact to them. They almost certainly already disable these kinds of codecs in their build. They reported this for the good of the ecosystem and the millions of users who were vulnerable.
- esrauch 1y agoGoogle does not "want this fixed", this isn't a bug report from a team using ffmpeg, it's a security analysis from a whitehat security project. I think really if there's all these machine generated meaningless security reports, wasting time with that sounds like a very sensible complaint, but then they should point at that junk as the problem. But for the specific CVE discussed it really looks to me like they are doing everything right: it's a real, default-configuration exploitable issue, they reported it and ffmpeg didn't fix or ask for any extension then it gets publicly disclosed after 90 days per a standard security disclosure policy.
- NegativeK 1y agoAGPL, with no CLA that lets the owners relicense. Then we'll see if the using corporation fully believes in open source. There's a reason Google turned into year 2000 Microsoft "it's viral!" re. the AGPL. They're less able to ignore the intent of the license and lock away their changes.
- bigstrat2003 1y agoThere is nothing whatsoever that the GPL would do to change this situation. Bringing up the permissive license debate is a non-sequitur here.
- EasyMark 1y agoWhat in GPL3 or MIT mandates that Google fix this bug and submit a PR or simply sends a bug report and walks away? I don't see how this applies at all.
- tpmoney 1y agoffmpeg is already LGPL / GPLv2. How does the license choice factor into this at all?
- iscoelho 1y agoGoogle is, at no cost to FFMPEG: 1) dedicating compute resources to continuously fuzzing the entire project 2) dedicating engineering resources to validating the results and creating accurate and well-informed bug reports (in this case, a seriously underestimated security issue) 3) additionally for codecs that Google likely does not even internally use or compile, purely for the greater good of FFMPEG's user base Needless to say, while I agree Google has a penny to spare to fund FFMPEG, and should (although they already contribute), I do not agree with funding this maintainer.
- pjmlp 1y agoThen they can surely also provide a pull request for said CVE.
- SR2Z 1y agoWhere do you draw the line? Do you want Google to just not inspect any projects that it can't fully commit to maintaining? Providing a real CVE is a contribution, not a burden. The ffmpeg folks can ignore it, since by all indications it's pretty minor.
- strictnein 1y agoPersonally, I want the $3.5 Trillion company to do more. So the line should be somewhere else.
- SR2Z 1y agoSo you don't have a line, you just want to move the goalposts and keep moving them?
- iscoelho 1y agoIt is my understanding that the commenters in FFMPEG's favor believe that Google is doing a disservice by finding these security vulnerabilities, as they require volunteer burden to patch, and that they should either: 1) allow the vulnerabilities to remain undiscovered & unpatched zero-days (stop submitting "slop" CVEs.) 2) supply the patches (which i'm sure the goalpost will move to the maintainers being upset that they have to merge them.) 3) fund the project (including the maintainers who clearly misunderstand the severity of the vulnerabilities and describe them as "slop") (no thank you.) This entire thread defies logic.