[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DA4CCD6.4060006@mvista.com>
Date: Tue, 12 Apr 2011 12:06:14 -1000
From: akuster <akuster@...sta.com>
To: oss-security@...ts.openwall.com
CC: Josh Bressers <bressers@...hat.com>
Subject: Re: Closed list
Josh,
Your initial e-mail indicated we would be part of this new group since
we where a vendor-sec member. Now there are new requirements we have to
meet. Is there a possibility of a probationary period so we can try to
comply to these new requirements and still be on the closed list?
Mahalo,
Armin
On 04/01/2011 08:03 AM, Josh Bressers wrote:
> Hello everyone,
>
> This topic has lost focus lately. Rather than let it slip away, I think we
> should go ahead with the simplest solution right now, we can always do
> something different at a future date.
>
> Openwall has graciously volunteered to run a new list, and they currently
> have some infrastructure in place to do this. The new list can start up
> right away. In this instance, I fear perfect is the enemy of the good. I'd
> rather see something functional in place than nothing.
>
> Here is the plan for initial membership (this is also approved by
> Openwall).
>
> 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).
>
> Once we have an initial seed group, we can focus on future membership
> ideas.
>
> Thanks.
>
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.
