All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Pascal Bouchareine <pascal@gandi.net>,
	xen-devel@lists.xensource.com,
	John Levon <levon@movementarian.org>
Subject: Re: [PATCH] [Xend] Move some backend configuration
Date: Tue, 30 Sep 2008 17:35:52 +0100	[thread overview]
Message-ID: <20080930163552.GF15442@redhat.com> (raw)
In-Reply-To: <C5080DC1.279C8%keir.fraser@eu.citrix.com>

On Tue, Sep 30, 2008 at 05:09:21PM +0100, Keir Fraser wrote:
> On 30/9/08 16:30, "Daniel P. Berrange" <berrange@redhat.com> wrote:
> 
> > Console data
> > 
> >  /local/domain/%d/console/vnc-port
> >  /local/domain/%d/console/tty
> 
> Duplicating this pair of nodes sounds fine to me, *but* then libvirt is
> simply remaining vulnerable to the kind of attack we're are looking to
> avoid? Can any good really come from keeping the old locations?

Given that this is security sensitive, I have no objection to updating
libvirt to read from the new locations. The only thing I need to work 
out is a reliable way to choose when to use the new location, vs the 
looking at old location (for compat with existing deployments). 

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  parent reply	other threads:[~2008-09-30 16:35 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 [this message]
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
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=20080930163552.GF15442@redhat.com \
    --to=berrange@redhat.com \
    --cc=keir.fraser@eu.citrix.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.