Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 03 Mar 2013 19:26:25 -0700
From: Kurt Seifried <>
CC: Michael Gilbert <>
Subject: Re: CVE id request: busybox

Hash: SHA1

On 03/03/2013 01:06 PM, Michael Gilbert wrote:
> On Sun, Mar 3, 2013 at 2:50 PM, Kurt Seifried wrote:
>> This actually raises a good point, due to Debian being a
>> secondary source in most cases (e.g. upstream has a bug report
>> which is then copied into Debian's bug tracker since Debian ships
>> it) the dates and sometimes information is wrong.
> Aren't these problems true for any source whether it be primary, 
> secondary, tertiary, or so on?

Sorry yeah I should have been more clear. This goes for all the major
secondary sources (Debian, SUSE, etc.).

>> I will no longer be issuing CVE's for issues brought up through
>> the Debian bugtracker without an original source to back it up,
>> otherwise more mistakes will happen which is not good.
> I don't understand the purpose of excluding an entire project's 
> sources.  Should redhat's bugzilla, gentoo, etc. also be excluded
> for the same reason?  If not, why do they get special treatment?

I didn't say I;'m excluding them. I simply will require an original
source, in this case the year is probably wrong.

> Is there really a problem at all?  The debian report included the 
> upstream commit, so you had a link to a primary resource anyway.
> So, I think a simple solution to this 'problem' of secondary
> sources is follow them to the primary one?

Yeah, and people can post them to the list. As stated before, I assign
a lot of CVEs. One minute extra per CVE is about 20 hours a year. It
adds up. So from now on I'll be needing original source confirmation
in the emails to oss-sec.

> Best wishes, Mike

- -- 
Kurt Seifried Red Hat Security Response Team (SRT)
PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993

Version: GnuPG v1.4.13 (GNU/Linux)


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.