From: Chris Wright <chrisw@osdl.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: security contact draft
Date: Thu, 13 Jan 2005 14:12:29 -0800 [thread overview]
Message-ID: <20050113141229.G24171@build.pdx.osdl.net> (raw)
In-Reply-To: <87mzvd9f9a.fsf@deneb.enyo.de>; from fw@deneb.enyo.de on Thu, Jan 13, 2005 at 10:43:29PM +0100
* Florian Weimer (fw@deneb.enyo.de) wrote:
> * Chris Wright:
>
> > To keep the conversation concrete, here's a pretty rough stab at
> > documenting the policy.
>
> Looks fine. Maybe you can add the following section?
>
> 3) Non-disclosure agreements
>
> The Linux kernel security contact is not a formal body and therefore
> unable to enter any non-disclosure agreements.
>
> UNIRAS and probably others require NDAs from affected software vendors
> before they share vulnerability information. It makes things easier
> if you state upfront that you won't play such games.
Fair point, I can add that easily.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-01-13 23:21 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 [this message]
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
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=20050113141229.G24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=fw@deneb.enyo.de \
--cc=linux-kernel@vger.kernel.org \
/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