From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Pascal Bouchareine <pascal@gandi.net>
Cc: xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>,
John Levon <levon@movementarian.org>
Subject: Re: [PATCH] [Xend] Move some backend configuration
Date: Thu, 02 Oct 2008 11:28:05 +0100 [thread overview]
Message-ID: <C50A60C5.27A3B%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <18660.41157.41727.193987@mariner.uk.xensource.com>
On 2/10/08 11:21, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
>> writing into device allows the guest to rewrite it's backend
>> location, this should be protected too i guess ?
>
> We will arrange for the backend location not to be trusted by anything
> important. In fact, it is entirely formulaic: if you know which
> domain the backend is supposed to be in, you can simply shuffle the
> path components. And you can double check against the backend's
> frontend path.
If you know the backend domid this works great. You don't need to check
anything in this case. If you try to validate the frontend's backend
reference then that's hard: strictly speaking you can only trust the
/local/domain/0 path prefix since otherwise two domains could collude to
redirect you to a backend directory under their control (or a domain could
point you at a 'backend directory' under its own path prefix, for example).
So this approach really only works for backends known to be in dom0 (which
of course is true for the vast majority of Xen installations). Hence xend is
storing the backend path under /vm where it's safe. Equally it could store
only the backend-id and construct the backend path from that.
-- Keir
next prev parent reply other threads:[~2008-10-02 10:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 14:24 [PATCH] [Xend] Move some backend configuration Pascal Bouchareine
2008-09-30 14:43 ` John Levon
2008-09-30 14:48 ` Keir Fraser
2008-09-30 14:58 ` John Levon
2008-09-30 15:09 ` Keir Fraser
2008-09-30 15:14 ` Ian Jackson
2008-09-30 15:30 ` Daniel P. Berrange
2008-09-30 16:09 ` Keir Fraser
2008-09-30 16:35 ` John Levon
2008-09-30 17:21 ` Pascal Bouchareine
2008-09-30 16:35 ` Daniel P. Berrange
2008-09-30 16:39 ` John Levon
2008-09-30 16:46 ` Keir Fraser
2008-09-30 17:08 ` Daniel P. Berrange
2008-09-30 17:09 ` Pascal Bouchareine
2008-10-02 9:34 ` Ian Jackson
2008-10-02 9:49 ` Keir Fraser
2008-10-02 10:16 ` Pascal Bouchareine
2008-10-02 10:20 ` Keir Fraser
2008-10-02 10:21 ` Ian Jackson
2008-10-02 10:28 ` Keir Fraser [this message]
2008-10-02 10:31 ` Ian Jackson
2008-10-02 13:45 ` John Levon
2008-10-02 14:04 ` Keir Fraser
2008-10-02 14:09 ` Keir Fraser
2008-10-02 15:09 ` John Levon
2008-10-02 15:25 ` Keir Fraser
2008-10-02 17:21 ` John Levon
2008-10-02 14:16 ` Ian Jackson
2008-09-30 15:11 ` Pascal Bouchareine
2008-09-30 15:02 ` Keir Fraser
2008-09-30 15:06 ` John Levon
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=C50A60C5.27A3B%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=berrange@redhat.com \
--cc=levon@movementarian.org \
--cc=pascal@gandi.net \
--cc=xen-devel@lists.xensource.com \
/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.