On Tue, Sep 30, 2008 at 03:58:18PM +0100, John Levon wrote:
> Precisely the problem, there's absolutely no idea or indication what is
> and isn't private. Thus you get libvirt looking in places it maybe
> shouldn't, but how are they supposed to know?
> I'm pretty sure this patch breaks libvirt again.
This might not break too much stuff as we kept the original backend
path(s) at their location. Most obvious fix for other clients is
changing the reading of the backend location from the frontend directory,
but the old behaviour still works.
However, some parts (the console tty, location) have changed and
> If it's a security fix (and I see the issue), it needs to be much more
> public than this patch was, and of course backported to at least 3.2
It might well be a security fix, even if this sounds like a moderate
I agree this requires a quick update, but we need to discuss it here
before publicizing ?
\o/ Pascal Bouchareine - Gandi
g 0170393757 15, place de la Nation - 75011 Paris
Xen-devel mailing list