public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: security contact draft
Date: Thu, 13 Jan 2005 22:43:29 +0100	[thread overview]
Message-ID: <87mzvd9f9a.fsf@deneb.enyo.de> (raw)
In-Reply-To: <20050113125503.C469@build.pdx.osdl.net> (Chris Wright's message of "Thu, 13 Jan 2005 12:55:03 -0800")

* 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.

  parent reply	other threads:[~2005-01-13 21:56 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 [this message]
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

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=87mzvd9f9a.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=chrisw@osdl.org \
    --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