[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4F21893B.2020306@redhat.com>
Date: Thu, 26 Jan 2012 10:11:23 -0700
From: Kurt Seifried <kseifried@...hat.com>
To: oss-security@...ts.openwall.com
Subject: Re: Request for CVE for Vulnerability in Tahoe-LAFS
1.9.0
And that's why I'm wanting people to include source code commit
information in their requests (the system works!!! =).
On 01/26/2012 08:12 AM, Patrick R McDonald wrote:
> On Thu, Jan 26, 2012 at 03:57:14PM +0100, Christian Hoffmann
> wrote:
>> Hallo Patrick,
>>
>> On 26.01.2012 15:15, Patrick R McDonald wrote:
>>> I would like to request a CVE for a vulnerability in
>>> Tahoe-LAFS,
>>>
>>> https://tahoe-lafs.org/pipermail/tahoe-announce/2012-January/000032.html
>>
>>>
I think CVE-2012-0051 has already been assigned to this vulnerability.
>>
>> It is referenced in the Trac ticket (see below) which is
>> mentioned in the above mail archive post, unless I'm confusing
>> things.
>>
>>
>> References: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654
>> http://seclists.org/oss-sec/2012/q1/135 (initial request)
>> http://seclists.org/oss-sec/2012/q1/158 (CVE assignment)
>>
>>
>> Best regards,
>>
>> Christian Hoffmann
>>
>
> My apologies. Thanks for the info and the quick turnaround.
--
Kurt Seifried Red Hat Security Response Team (SRT)
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.
