ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
	Andy Lutomirski <luto@amacapital.net>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	mchehab+samsung@kernel.org,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Handling of embargoed security issues
Date: Sun, 09 Sep 2018 18:48:36 +0100	[thread overview]
Message-ID: <1536515316.5768.48.camel@infradead.org> (raw)
In-Reply-To: <20180909172039.GE22251@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]

On Sun, 2018-09-09 at 13:20 -0400, Theodore Y. Ts'o wrote:
> 
> The only middle ground is "gentleman's agreement".  The main problem
> any legal agreement is what are the teeth if someone violates the NDA
> and breaks the embargo.  The reason why it will be very hard for some
> third-party, like the LF, to sign any kind of NDA on behalf of
> independent developers is that it puts the liability risk on the LF.
> And the LF's lawyers aren't going to be comfortable with this.
> 
> We've been through this before with the TAB and getting all of the TAB
> members under an NDA so we could talk about pre-standardized UEFI
> proposals.  We looked at trying to get the LF to sign an NDA for the
> TAB members who didn't work for companies which had an NDA with UEFI,
> and it just didn't work.  Ultimately, what we did is we negotiated a
> specific NDA just for me (where it would be my house on the line in
> terms of an NDA violation), and I then had to get the Google's lawyers
> to OK my signing it as a personal NDA.  The whole process took
> **months**.

In practice there's not really a lot of difference between a "real" NDA
and a gentlepersons' agreement. Nobody's *really* going to lose their
house; all that's likely to happen if you screw up is that they won't
include you in the party next time round.

We *had* a breach before the Spectre/Meltdown embargo was supposed to
be over, and to my knowledge (and I *hope*) nothing actually happened
except a bit of tutting.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]

  reply	other threads:[~2018-09-09 17:48 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 19:18 Jiri Kosina
2018-09-06 20:56 ` Linus Torvalds
2018-09-06 21:14   ` Jiri Kosina
2018-09-06 22:51     ` Eduardo Valentin
2018-09-07  9:17   ` Jani Nikula
2018-09-07 14:43   ` David Woodhouse
2018-09-06 22:55 ` Eduardo Valentin
2018-09-07  8:21   ` Geert Uytterhoeven
2018-09-10 23:26     ` Eduardo Valentin
2018-09-11  8:45       ` Greg KH
2018-09-11 17:10         ` Dave Hansen
2018-09-11 18:28           ` Greg KH
2018-09-11 18:44           ` Thomas Gleixner
2018-09-07 13:30   ` Jiri Kosina
2018-09-09 12:55     ` Greg KH
2018-09-09 19:48       ` Jiri Kosina
2018-09-10  4:04         ` Eduardo Valentin
2018-09-12  7:03           ` Greg KH
2018-09-10  4:12       ` Eduardo Valentin
2018-09-10 11:10       ` Mark Brown
2018-09-12  4:22   ` Balbir Singh
2018-09-08  4:21 ` Andy Lutomirski
2018-09-08  8:56   ` Thomas Gleixner
2018-09-08 11:21     ` Mauro Carvalho Chehab
2018-09-08 11:34       ` Greg KH
2018-09-08 14:20         ` Andy Lutomirski
2018-09-08 15:29           ` Greg KH
2018-09-08 15:00         ` James Bottomley
2018-09-08 15:32           ` Greg KH
2018-09-08 15:54             ` James Bottomley
2018-09-08 19:49               ` Linus Torvalds
2018-09-08 21:24                 ` James Bottomley
2018-09-08 22:33                   ` Andy Lutomirski
2018-09-09 12:18                     ` Mauro Carvalho Chehab
2018-09-10 22:59                 ` Dave Hansen
2018-09-11  8:48                   ` Greg KH
2018-09-09 12:51               ` Greg KH
2018-09-09 14:20                 ` Linus Torvalds
2018-09-09 14:38                   ` James Bottomley
2018-09-09 14:51                     ` Andy Lutomirski
2018-09-09 17:20                       ` Theodore Y. Ts'o
2018-09-09 17:48                         ` David Woodhouse [this message]
2018-09-09 18:17                         ` Andy Lutomirski
2018-09-09 18:56                           ` Theodore Y. Ts'o
2018-09-09 19:19                             ` Andy Lutomirski
2018-09-09 20:20                             ` Jiri Kosina
2018-09-09 21:36                               ` James Bottomley
2018-09-10  9:25                             ` Thomas Gleixner
2018-09-10 14:40                               ` James Bottomley
2018-09-11  8:20                               ` Jiri Kosina
2018-09-11  9:03                                 ` Thomas Gleixner
2018-09-09 19:41                   ` Jiri Kosina
2018-09-08 19:26           ` Jiri Kosina
2018-09-08 19:47             ` James Bottomley

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=1536515316.5768.48.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=luto@amacapital.net \
    --cc=mchehab+samsung@kernel.org \
    --cc=tytso@mit.edu \
    /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