On Wed, 2020-11-04 at 13:38 -0500, Ronald S. Bultje wrote: > > Hi Joakim, > > On Tue, Nov 3, 2020 at 8:57 AM Joakim Tjernlund < > joakim.tjernl...@infinera.com> wrote: > > > On Tue, 2020-11-03 at 14:38 +0100, Andreas Rheinhardt wrote: > > > > > > Timo Rothenpieler: > > > > Given the multitude of recent serious security issues in Chromium-Based > > > > Browsers, is this even still an issue? > > > > Anything not up to date enough to have already been fixed has serious > > > > security issues and should be updated ASAP, which also fixes this issue > > > > in turn. > > > > > > > > I'd rather see downstream users fix their stuff than introduce > > > > workarounds for broken downstreams into ffmpeg. > > > +1 > > > > Chromium has fixed this issue(but not sure if released yet though). Then > > this needs to trickle into > > elektron and finally into MS Teams(as an example). Will take time so it > > will be fixed at some point, not anytime soon though. > > > For clarity, could you explain how releasing this fix would not have to go > through the same release funnel in Chrome? Or is the Chrome dependency in > elektron/teams not the same as the FFmpeg dependency?
I don't understand what you are asking for... Jocke _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
