[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D99D975.5080700@redhat.com>
Date: Mon, 04 Apr 2011 22:45:09 +0800
From: Eugene Teo <eugene@...hat.com>
To: oss-security@...ts.openwall.com
CC: Ludwig Nussel <ludwig.nussel@...e.de>
Subject: Re: Closed list
On 04/04/2011 10:38 PM, Ludwig Nussel wrote:
> Josh Bressers wrote:
>> Initial members will have had to be a vendor-sec member (no exploders this
>> time around). You must reply to this thread, in public (on oss-security).
>> We want this to be very public, we have nothing to hide. You must have a
>> public gpg key ID included in your reply. The new list will gpg encrypt all
>> mail (it does accept plaintext messages though).
>
> I've created a dedicated key for this purpose:
>
> pub 2048R/1F334FA6 2011-04-04 [expires: 2012-04-03]
> uid Ludwig Nussel (vendor-sec)<ludwig.nussel@...e.de>
> sub 2048R/4F5FEB97 2011-04-04 [expires: 2012-04-03]
Maybe once we have a list of initial members, we should start using a
vouching system, that the applicant must be referred by someone from the
list, and we only accept members whom we met and trust. Just a suggestion.
Eugene
--
main(i) { putchar(182623909 >> (i-1) * 5&31|!!(i<7)<<6) && main(++i); }
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.
