From: Chris Wright <chrisw@osdl.org>
To: Patrick Plattes <patrick@erdbeere.net>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: security contact draft
Date: Thu, 3 Feb 2005 10:08:58 -0800 [thread overview]
Message-ID: <20050203100858.H24171@build.pdx.osdl.net> (raw)
In-Reply-To: <20050203142837.GA30981@erdbeere.net>; from patrick@erdbeere.net on Thu, Feb 03, 2005 at 03:28:37PM +0100
* Patrick Plattes (patrick@erdbeere.net) wrote:
> i think security mailing list is a good idea. normally i would prefere a
> full open list, but in some cases this could be the right way.
>
> i have an additional idea. maybe it is useful to push the mails on the
> list into publc space automaticly after a delay of $NUMDAYS+$MAX -
> according to alans idea. with this little feature we could be sure, that
> no security report will be 'forgotten'.
>
> this 'public space' could be an open security list where anyone else is
> able to comment reports, fixes and bugs.
We had actually discussed this. It's mainly a difficulty in managing
such an idea, nobody was opposed to it.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2005-02-03 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 20:55 security contact draft Chris Wright
2005-01-13 20:10 ` Alan Cox
2005-01-13 21:31 ` Linus Torvalds
2005-01-13 19:28 ` Marcelo Tosatti
2005-01-13 22:02 ` Chris Wright
2005-01-13 21:43 ` Florian Weimer
2005-01-13 22:12 ` Chris Wright
2005-01-15 0:33 ` Alan Cox
2005-01-15 2:43 ` Chris Wright
2005-01-15 4:00 ` Alan Cox
2005-01-18 0:24 ` security contact draft2 (was Re: security contact draft) Chris Wright
2005-01-18 17:39 ` Horst von Brand
2005-02-03 14:28 ` security contact draft Patrick Plattes
2005-02-03 18:08 ` Chris Wright [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050203100858.H24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@erdbeere.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).