Hi ffmpeg-user,
I wanted to share news of a 3rd No Time to Wait conference, hosted by the
British Film Institute, on the theme of the intersection of open media, open
standards, and audiovisual preservation. With support from our host (thx BFI)
and our sponsors, the registration is free.
Is 2.8.14 up-to-date as far as known security issues (e.g CVE's) are
concerned?
Looking at CVE's for ffmpeg, some will say "3.x.y and before" - does that
mean that they only affect 3.x? If not and they affect 2.8.14, then there
are a decent number that affect 2.8.14 (15 of them?)
For example,
Am 15.05.2018 um 22:02 schrieb Bryan Duff:
> Is 2.8.14 up-to-date as far as known security issues (e.g CVE's) are
> concerned?
>
> Looking at CVE's for ffmpeg, some will say "3.x.y and before" - does that
> mean that they only affect 3.x? If not and they affect 2.8.14, then there
> are a
On 5/15/18, Bryan Duff wrote:
> Is 2.8.14 up-to-date as far as known security issues (e.g CVE's) are
> concerned?
>
> Looking at CVE's for ffmpeg, some will say "3.x.y and before" - does that
> mean that they only affect 3.x? If not and they affect 2.8.14, then there
> are a
2018-05-15 22:02 GMT+02:00, Bryan Duff :
> Is 2.8.14 up-to-date as far as known security issues (e.g
> CVE's) are concerned?
2.8 is still supported and gets security updates:
http://ffmpeg.org/download.html
Note that nearly no fixed FFmpeg security issue gets a CVE,
so CVE's
2018-05-16 0:25 GMT+02:00, Bryan Duff :
> On Tue, May 15, 2018 at 4:46 PM, Carl Eugen Hoyos wrote:
[...]
>> Could you elaborate what you want to know exactly?
>> The issue in question was introduced after 2.8 was released but
>> I wonder why you chose this example: This is a
On Tue, May 15, 2018 at 4:46 PM, Carl Eugen Hoyos
wrote:
> 2018-05-15 22:02 GMT+02:00, Bryan Duff :
> > Is 2.8.14 up-to-date as far as known security issues (e.g
> > CVE's) are concerned?
>
> 2.8 is still supported and gets security updates:
>