Joakim Tjernlund: > 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. > The issue was fixed on August 11: https://chromium.googlesource.com/chromium/src/+/7f4c7ff6b0f0e74338c885b0d5e5ef80fed597c3 It is contained in releases > 86.0.4232.0.
- Andreas _______________________________________________ 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".
