WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] [Xend] Move some backend configuration

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [Xend] Move some backend configuration
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 30 Sep 2008 17:46:04 +0100
Cc: Pascal Bouchareine <pascal@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 30 Sep 2008 09:46:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080930163552.GF15442@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckjHAb7RdNNB48PEd2xRgAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] [Xend] Move some backend configuration
User-agent: Microsoft-Entourage/11.4.0.080122
On 30/9/08 17:35, "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:

>> 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).

That's an interesting question. Obviously you don't want to race their
creation and go down the unsafe path unnecessarily.

We could add a node to xenstore, or append version/feature info to the pid
file? Do you have a preference?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel