Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130725100200.GA28446@videolan.org>
Date: Thu, 25 Jul 2013 12:02:00 +0200
From: Jean-Baptiste Kempf <jb@...eolan.org>
To: Kurt Seifried <kseifried@...hat.com>
Cc: oss-security@...ts.openwall.com, Michael Niedermayer <michaelni@....at>,
	Moritz Muehlenhoff <jmm@...til.org>,
	Moritz Muehlenhoff <jmm@...ian.org>, ffmpeg-security@...peg.org,
	security@...eolan.org
Subject: Re: new FFMpeg stuff

On 25 Jul, Kurt Seifried wrote :
> > Why the VLC security team should be involved in that?
> 
> Because they want to help make sure the CVEs get correctly assigned?
> 
> If you guys don't care about getting CVE's done properly well that's
> your choice I guess and I'll assign the CVEs as best I can. But I was
> hoping VLC upstream might help out.

I think you misunderstood me.
Upstream is FFmpeg, not VLC. Why shouldn't FFmpeg team get the CVE?

Best regards,

-- 
Jean-Baptiste Kempf
http://www.jbkempf.com/ - +33 672 704 734
Sent from my Electronic Device

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.