4 ms·

One can argue that for a user it doesn't matter if it's ffmpeg, VLC or something else that's buggy. A user is installing VLC, has probably no knowledge of what

by maaaats 13y ago

One can argue that for a user it doesn't matter if it's ffmpeg, VLC or something else that's buggy. A user is installing VLC, has probably no knowledge of what ffmpeg is, and it's the use of VLC that exposes the user to the security bug. As such, it's VLC responsibility to not ship a product that may harm a user's computer, even if the error is not in their code.

PhantomLobe 13y ago
> A user is installing VLC, has probably no knowledge of what ffmpeg is, and it's the use of VLC that exposes the user to the security bug. A user that won't care about that will neither care about Secunia.
jbk 13y ago
All the known vulnerabilities have been fixed. Which one are you referring to?
- maaaats 13y ago
  None in particular, just the general concept that you are responsible for all the parts in the end product, even if not made by you.
  - jbk 13y ago
    Oh, yes, we agree on that. Which is why we patched FFmpeg for the SWF issue.