xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: Jan Beulich <JBeulich@suse.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Lars Kurth <lars.kurth@xen.org>, Matt Wilson <msw@amazon.com>
Subject: Re: Security discussion: Summary of proposals and criteria (was Re: Security vulnerability process, and CVE-2012-0217)
Date: Mon, 9 Jul 2012 14:51:01 +0100	[thread overview]
Message-ID: <20120709135101.GA83420@ocelot.phlegethon.org> (raw)
In-Reply-To: <4FFAC0FF.6040206@invisiblethingslab.com>

At 13:31 +0200 on 09 Jul (1341840671), Joanna Rutkowska wrote:
> If you're into security industry (going to conferences, etc) you
> certainly know the right people who would be delight to buy exploits
> from you, believe me ;) Probably most Xen developers don't fit into this
> crowd, true, but then again, do you think it would be so hard for an
> interested organization to approach one of the Xen developers on the
> pre-disclousure list? How many would resist if they had a chance to cash
> in some 7-figure number for this (I read in the press that hot
> bugs/exploits sell for this amount actually)?

I think the argument is that an exploit that's going to be public (and
patched) in the next couple of weeks would not fetch the same kind of
price as a unknown attack that can be kept for later.

OTOH, I'm sure it's worth something for chance to get in early and
install a rootkit, or just crash your rivals' systems for the bad
publicity.

I'm not sure there's an enormous difference between a leaky
predisclosure list and full disclosure, but FWIW I'm in favour of 
(a) having a list, and (b) keeping the embargo at no more than two weeks.

Tim.

  parent reply	other threads:[~2012-07-09 13:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 16:46 Security discussion: Summary of proposals and criteria (was Re: Security vulnerability process, and CVE-2012-0217) George Dunlap
2012-07-08  7:30 ` Joanna Rutkowska
2012-07-09  9:23   ` George Dunlap
2012-07-09 11:31     ` Joanna Rutkowska
2012-07-09 13:25       ` Joanna Rutkowska
2012-07-09 13:35         ` Keir Fraser
2012-07-09 13:40           ` Joanna Rutkowska
2012-07-09 13:51       ` Tim Deegan [this message]
2012-07-09 14:08         ` Joanna Rutkowska
2012-07-12 16:34           ` Stefano Stabellini
2012-07-12 16:47             ` Joanna Rutkowska
2012-07-12 17:00               ` Stefano Stabellini
2012-07-12 17:22                 ` Joanna Rutkowska
2012-07-13 18:15                   ` Stefano Stabellini
2012-07-14  0:18 ` Security discussion: Summary of proposals and criteria Matt Wilson
2012-07-16 17:56   ` George Dunlap
2012-08-03 17:31 ` Security discussion: Summary of proposals and criteria (was Re: Security vulnerability process, and CVE-2012-0217) George Dunlap
2012-08-06  6:55   ` Jan Beulich

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=20120709135101.GA83420@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=joanna@invisiblethingslab.com \
    --cc=lars.kurth@xen.org \
    --cc=msw@amazon.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).