All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Keir Fraser <keir@xen.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xenstored: allow guests to reintroduce themselves
Date: Tue, 9 Aug 2011 13:33:21 +0100	[thread overview]
Message-ID: <4E412911.4020306@eu.citrix.com> (raw)
In-Reply-To: <CA66D91A.30242%keir@xen.org>

On 08/09/2011 12:31 PM, Keir Fraser wrote:
> Do you have any examples of projects which could run with much lesser
> privilege, and very constrained xenstore access, if a suitably controlled
> xenstore interface was provided?

There's a bunch of program that doesn't need much more than read/write to a specific limited part of xenstore.

- Guest agents (reporting stats usually)
- things listening to some actions (snapshot yourself, export some storage thing, etc..)

Perhaps a variant of the restrict packet would be enough to drop some privileges
of the xenbus connection (at connection time) to read/write to a specific path.

-- 
Vincent

  reply	other threads:[~2011-08-09 12:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 12:38 [PATCH] xenstored: allow guests to reintroduce themselves Olaf Hering
2011-08-09  8:59 ` Ian Campbell
2011-08-09  9:17   ` Olaf Hering
2011-08-09  9:25     ` Ian Campbell
2011-08-09  9:34       ` Olaf Hering
2011-08-09 10:08 ` Vincent Hanquez
2011-08-09 10:14   ` Keir Fraser
2011-08-09 10:50     ` Vincent Hanquez
2011-08-09 11:00       ` Keir Fraser
2011-08-09 11:18         ` Vincent Hanquez
2011-08-09 11:31           ` Keir Fraser
2011-08-09 12:33             ` Vincent Hanquez [this message]
2011-08-09 11:07     ` Vincent Hanquez
2011-08-09 10:49   ` Olaf Hering
2011-08-09 16:34 ` Ian Jackson
2011-08-09 16:38   ` Ian Jackson
2011-08-09 16:49 ` Ian Jackson

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=4E412911.4020306@eu.citrix.com \
    --to=vincent.hanquez@eu.citrix.com \
    --cc=keir@xen.org \
    --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.