From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] [Xend] Move some backend configuration Date: Tue, 30 Sep 2008 17:46:04 +0100 Message-ID: References: <20080930163552.GF15442@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080930163552.GF15442@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Daniel P. Berrange" Cc: Pascal Bouchareine , xen-devel@lists.xensource.com, John Levon List-Id: xen-devel@lists.xenproject.org On 30/9/08 17:35, "Daniel P. Berrange" 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