{"id":277018,"date":"2025-11-11T20:16:11","date_gmt":"2025-11-11T20:16:11","guid":{"rendered":"https:\/\/www.newsbeep.com\/ca\/277018\/"},"modified":"2025-11-11T20:16:11","modified_gmt":"2025-11-11T20:16:11","slug":"ffmpeg-to-google-fund-us-or-stop-sending-bugs","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/ca\/277018\/","title":{"rendered":"FFmpeg to Google: Fund Us or Stop Sending Bugs"},"content":{"rendered":"<p>You may never have heard of <a href=\"https:\/\/www.ffmpeg.org\/\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">FFmpeg<\/a>, but you\u2019ve used it. This <a href=\"https:\/\/thenewstack.io\/the-reality-of-open-source-more-puppies-less-beer\/\" class=\"local-link\" rel=\"nofollow noopener\" target=\"_blank\">open source<\/a> program\u2019s robust multimedia framework is used to process video and audio media files and streams across numerous platforms and devices. It provides tools and libraries for format conversion, aka transcoding, playback, editing, streaming, and post-production effects for both audio and video media.<\/p>\n<p>FFmpeg\u2019s libraries, such as <a href=\"https:\/\/ffmpeg.org\/libavcodec.html\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">libavcodec<\/a> and <a href=\"https:\/\/ffmpeg.org\/doxygen\/trunk\/group__libavf.html\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">libavformat<\/a>, are essential for media players and software, including VLC, Kodi, Plex, Google Chrome, Firefox, and even YouTube\u2019s video processing backend. It is also, like many other vital <a href=\"https:\/\/thenewstack.io\/can-open-source-sustain-itself-without-losing-its-soul\/\" class=\"local-link\" rel=\"nofollow noopener\" target=\"_blank\">open source programs, terribly underfunded<\/a>.<\/p>\n<p>Corporate Responsibility vs. Volunteer Labor<\/p>\n<p>A lively debate on Twitter began between <a href=\"https:\/\/www.linkedin.com\/in\/danlorenc\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">Dan Lorenc<\/a>, CEO and co-founder of <a href=\"https:\/\/www.chainguard.dev\/?utm_content=inline+mention\" class=\"ext-link\" target=\"_blank\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\">Chainguard<\/a>, the software supply chain security company, the FFmpeg project, <a href=\"https:\/\/cloud.google.com\/?utm_content=inline+mention\" class=\"ext-link\" target=\"_blank\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\">Google<\/a>, and security researchers over security disclosures and the responsibilities of large tech companies in open-source software.<\/p>\n<p>The core of the discussion revolves around how vulnerabilities should be reported, who is responsible for fixing them, and the challenges that arise when AI is used to uncover a flood of potentially meaningless security issues. But at heart, it\u2019s about money.<\/p>\n<p>An Obscure Bug Ignites the Controversy<\/p>\n<p>This discussion has been heating up for some time. In mid-October, FFmpeg tweeted that \u201c<a href=\"https:\/\/x.com\/FFmpeg\/status\/1979066506030793116\" class=\"ext-link\" rel=\"external  nofollow\" onclick=\"this.target=&#039;_blank&#039;;\">security issues are taken extremely seriously in FFmpeg<\/a>, but fixes are written by volunteers.\u201d This point cannot be emphasised enough. As FFmpeg tweeted later, \u201c<a href=\"https:\/\/x.com\/FFmpeg\/status\/1982592087494398164\" class=\"ext-link\" rel=\"external  nofollow\" onclick=\"this.target=&#039;_blank&#039;;\">FFmpeg is written almost exclusively by volunteers.<\/a>\u201d<\/p>\n<p>Thus, as <a href=\"https:\/\/www.linkedin.com\/in\/-mark-atwood\/\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">Mark Atwood<\/a>, an open source policy expert, pointed out on Twitter, he had to keep telling <a href=\"https:\/\/aws.amazon.com\/?utm_content=inline+mention\" class=\"ext-link\" target=\"_blank\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\">Amazon<\/a> to not do things that would mess up FFmpeg because, he had to keep explaining to his bosses that \u201c<a href=\"https:\/\/x.com\/_Mark_Atwood\/status\/1978888607298691279\" class=\"ext-link\" rel=\"external  nofollow\" onclick=\"this.target=&#039;_blank&#039;;\">They are not a vendor, there is no NDA, we have no leverage,<\/a> your VP has refused to help fund them, and they could kill three major product lines tomorrow with an email. So, stop, and listen to me \u2026 \u201d<\/p>\n<p>The Growing Burden on Open Source Maintainers<\/p>\n<p>The latest episode was sparked after a Google AI agent found an especially obscure bug in FFmpeg. How obscure? This \u201c<a href=\"https:\/\/issuetracker.google.com\/issues\/440183164\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">medium impact issue in ffmpeg<\/a>,\u201d which the FFmpeg developers did patch, is \u201can issue with <a href=\"https:\/\/x.com\/FFmpeg\/status\/1983949866725437791\" class=\"ext-link\" rel=\"external  nofollow\" onclick=\"this.target=&#039;_blank&#039;;\">decoding LucasArts Smush codec<\/a>, specifically the first 10-20 frames of Rebel Assault 2, a game from 1995.\u201d<\/p>\n<p>Wow.<\/p>\n<p>FFmpeg added, \u201cFFmpeg aims to play every video file ever made.\u201d That\u2019s all well and good, but is that a valuable use of an assembly programmer\u2019s time? Oh, right, you may not know. FFmpeg\u2019s heart is assembly language. As a former assembly language programmer, it is not, in any way, shape, or form, easy to work with.<\/p>\n<p>As FFmpeg put it, this is \u201c<a href=\"https:\/\/x.com\/ffmpeg\/status\/1984207514389586050\" class=\"ext-link\" rel=\"external  nofollow\" onclick=\"this.target=&#039;_blank&#039;;\">CVE slop.<\/a>\u201d<\/p>\n<p>Many in the FFmpeg community argue, with reason, that it is unreasonable for a trillion-dollar corporation like Google, which heavily relies on FFmpeg in its products, to shift the workload of fixing vulnerabilities to unpaid volunteers. They believe Google should either provide patches with vulnerability reports or directly support the project\u2019s maintenance.<\/p>\n<p>Earlier, FFmpeg pointed out that it\u2019s far from the only open source project to face such issues.<\/p>\n<p>Specifically, the project team mentions <a href=\"https:\/\/www.linkedin.com\/in\/nwellnhof\/\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">Nick Wellnhofer<\/a>, the former maintainer of <a href=\"https:\/\/gitlab.gnome.org\/GNOME\/libxml2\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">libxml2<\/a>, a widely used open source software library for parsing Extensible Markup Language (XML). <a href=\"https:\/\/discourse.gnome.org\/t\/stepping-down-as-libxml2-maintainer\/31398\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">Wellnhofer recently resigned from maintaining libxml2 <\/a>because he had to \u201cspend several hours each week dealing with security issues reported by third parties. Most of these issues aren\u2019t critical, but it\u2019s still a lot of work.<\/p>\n<p>\u201cIn the long term, this is <a href=\"https:\/\/gitlab.gnome.org\/GNOME\/libxml2\/-\/issues\/913\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">unsustainable for an unpaid volunteer like me.<\/a> \u2026 In the long run, putting such demands on OSS maintainers without compensating them is detrimental. \u2026\u00a0 It\u2019s even more unlikely with Google Project Zero, the best white-hat security researchers money can buy, breathing down the necks of volunteers.\u201d<\/p>\n<p>Google\u2019s Controversial Security Disclosure Policy<\/p>\n<p>What made this a hot issue was that back in July, <a href=\"https:\/\/googleprojectzero.blogspot.com\/\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">Google Project Zero (GPZ)<\/a> announced a trial of its new <a href=\"https:\/\/googleprojectzero.blogspot.com\/2025\/07\/reporting-transparency.html\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">Reporting Transparency<\/a> policy. With this policy change, GPZ announces that it has reported an issue on a specific project within a week of discovery, and the security standard 90-day disclosure clock then starts, regardless of whether a patch is available or not.<\/p>\n<p>Many volunteer open source program maintainers and developers feel this is massively unfair to put them under such pressure when Google has billions to address the problem.<\/p>\n<p>FFmpeg tweeted, \u201c<a href=\"https:\/\/x.com\/FFmpeg\/status\/1984178359354483058\" class=\"ext-link\" rel=\"external  nofollow\" onclick=\"this.target=&#039;_blank&#039;;\">We take security very seriously<\/a>, but at the same time, is it really fair that trillion-dollar corporations run AI to find security issues in people\u2019s hobby code? Then expect volunteers to fix.\u201d<\/p>\n<p>True, Google does offer a <a href=\"https:\/\/bughunters.google.com\/about\/rules\/open-source\/4928084514701312\/patch-rewards-program-rules\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">Patch Rewards Program<\/a>, but as a Twitter user using the handle Ignix The Salamander observed, \u201c<a href=\"https:\/\/x.com\/ignixsalamander\/status\/1986111396095074689\" class=\"ext-link\" rel=\"external  nofollow\" onclick=\"this.target=&#039;_blank&#039;;\">FFmpeg already mentioned the program is too limited for them<\/a>, and they point out the three patches per month limit. Please don\u2019t assume people complain just for the sake of complaining, there is a genuine conflict between corporate security &amp; usage vs open source support IMHO.\u201d<\/p>\n<p>Lorenc argues back, in an e-mail to me, that \u201cCreating and publishing software under an open source license is an act of contribution to the digital commons. Finding and publishing information about security issues in that software is also an act of contribution to the same commons.<\/p>\n<p>\u201cThe position of the FFmpeg X account is that somehow disclosing vulnerabilities is a bad thing. Google provides more assistance to open source software projects than almost any other organization, and these debates are more likely to drive away potential sponsors than to attract them.\u201d<\/p>\n<p>Differing Perspectives on Vulnerability Disclosures<\/p>\n<p>The fundamental problem remains that the FFmpeg team lacks the financial and developer resources to address a flood of AI-created CVEs.<\/p>\n<p>On the other hand, security experts are certainly right in thinking that FFmpeg is a critical part of the Internet\u2019s technology framework and that security issues do need to be made public responsibly and addressed. After all, hackers can use AI to find vulnerabilities\u00a0in the same way Google does with its AI bug finder,\u00a0<a href=\"https:\/\/googleprojectzero.blogspot.com\/2024\/10\/from-naptime-to-big-sleep.html\" target=\"_blank\" rel=\"noopener external  nofollow\" class=\"ext-link\" onclick=\"this.target=&#039;_blank&#039;;\">Big Sleep<\/a>, and Google wants to identify\u00a0potential security holes ahead of them.<\/p>\n<p>The reality is, however, that without more support from the trillion-dollar companies that profit from open source, many woefully underfunded, volunteer-driven critical open-source projects will no longer be maintained at all.<\/p>\n<p>For example, <a href=\"https:\/\/discourse.gnome.org\/t\/stepping-down-as-libxml2-maintainer\/31398\" class=\"ext-link\" rel=\"external  nofollow noopener\" onclick=\"this.target=&#039;_blank&#039;;\" target=\"_blank\">Wellnhofer has said he will no longer maintain libxml2 in December<\/a>. Libxml2 is a critical library in all web browsers, web servers, LibreOffice and numerous Linux packages. We don\u2019t need any more arguments; we need real support for critical <a class=\"wpil_keyword_link local-link\" href=\"https:\/\/thenewstack.io\/open-source\/\" title=\"open source programs\" data-wpil-keyword-link=\"linked\" data-wpil-monitor-id=\"3320\" rel=\"nofollow noopener\" target=\"_blank\">open source programs<\/a> before we have another major security breach.<\/p>\n<p>\t<a class=\"row youtube-subscribe-block\" href=\"https:\/\/youtube.com\/thenewstack?sub_confirmation=1\" target=\"_blank\" rel=\"nofollow noopener\"><\/p>\n<p>\n\t\t\t\tYOUTUBE.COM\/THENEWSTACK\n\t\t\t<\/p>\n<p>\n\t\t\t\tTech moves fast, don&#8217;t miss an episode. Subscribe to our YouTube<br \/>\n\t\t\t\tchannel to stream all our podcasts, interviews, demos, and more.\n\t\t\t<\/p>\n<p>\t\t\t\tSUBSCRIBE<\/p>\n<p>\t<\/a><\/p>\n<p>    Group<br \/>\n    Created with Sketch.<\/p>\n<p>\t\t<a href=\"https:\/\/thenewstack.io\/author\/sjvn\/\" class=\"author-more-link\" rel=\"nofollow noopener\" target=\"_blank\"><\/p>\n<p>\t\t\t\t\t<img decoding=\"async\" class=\"post-author-avatar\" src=\"https:\/\/www.newsbeep.com\/ca\/wp-content\/uploads\/2025\/11\/cee63948-cropped-8a0b5c52-steven-vaughan-nichols.jpg\"\/><\/p>\n<p>\n\t\t\t\t\t\t\tSteven J. Vaughan-Nichols, aka sjvn, has been writing about technology and the business of technology since CP\/M-80 was the cutting-edge PC operating system, 300bps was a fast internet connection, WordStar was the state-of-the-art word processor, and we liked it.\t\t\t\t\t\t<\/p>\n<p>\t\t\t\t\t\tRead more from Steven J. Vaughan-Nichols\t\t\t\t\t\t<\/p>\n<p>\t\t<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"You may never have heard of FFmpeg, but you\u2019ve used it. This open source program\u2019s robust multimedia framework&hellip;\n","protected":false},"author":2,"featured_media":277019,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[49,48,61],"class_list":["post-277018","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology","tag-ca","tag-canada","tag-technology"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts\/277018","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/comments?post=277018"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts\/277018\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/media\/277019"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/media?parent=277018"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/categories?post=277018"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/tags?post=277018"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}