All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>,
	xen-devel@lists.xen.org, julien.grall@linaro.org, tim@xen.org,
	stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v3] xen/tools: Introduce QNX IFS loader
Date: Tue, 23 Sep 2014 19:20:58 +0100	[thread overview]
Message-ID: <1411496458.27559.26.camel@citrix.com> (raw)
In-Reply-To: <21537.42802.301581.714879@mariner.uk.xensource.com>

On Tue, 2014-09-23 at 18:00 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH v3] xen/tools: Introduce QNX IFS loader"):
> > On Tue, 2014-09-23 at 17:19 +0100, Ian Jackson wrote:
> > > These would all have been security bugs if the v3 patch had been
> > > accepted.  They would have been bugs that would potentially amount to
> > > privilege escalation for very many Xen installations.
> > 
> > Well, those booting untrusted QNX guests on ARM, which won't be many
> > yet, but point taken...
> 
> No.  The loader would run whenever it seems the appropriate image
> type, so everyone with it compiled in is vulnerable.

Yes, I realised this during dinner.

Ian.

  parent reply	other threads:[~2014-09-23 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 18:12 [PATCH v3] xen/tools: Introduce QNX IFS loader Oleksandr Tyshchenko
2014-09-22 18:12 ` Oleksandr Tyshchenko
2014-09-23 15:53   ` Ian Campbell
2014-09-23 16:19     ` Ian Jackson
2014-09-23 16:40       ` Ian Campbell
2014-09-23 17:00         ` Ian Jackson
2014-09-23 17:58           ` Oleksandr Tyshchenko
2014-09-23 18:20           ` Ian Campbell [this message]
2014-09-23 16:24     ` Oleksandr Tyshchenko
2014-09-23 16:37       ` Ian Campbell
2014-09-23 17:04         ` Oleksandr Tyshchenko

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=1411496458.27559.26.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=oleksandr.tyshchenko@globallogic.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.