[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qem

From: Daniel P. Berrange
Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qemu
Date: Thu, 5 Nov 2009 16:51:31 +0000
User-agent: Mutt/1.4.1i

On Thu, Nov 05, 2009 at 04:41:45PM +0000, Jamie Lokier wrote:
> Anthony Liguori wrote:
> > Absolutely.  I wanted to not have a hard dependency on PolicyKit to 
> > start out with but that's always been the plan.  I'd like to eventually 
> > add an optional PolicyKit dependency and when that's available not even 
> > bother with the qemu acl file.  The nice thing about PolicyKit is the 
> > desktop integration.  It's a much better user experience to allow a user 
> > to be prompted to allow qemu to access a bridge vs. having to error out 
> > to the user and tell them to muck with a config file.
> Please do keep it optional.
> PolicyKit is actively unhelpful when you're configuring a remote
> server which doesn't have a desktop, or you don't have access to it's
> desktop.
> It's also unhelpful when you're trying to script something.  The last
> thing you want a test harness script to do is prompt the user.

PolicyKit has no fundamental requirement for a graphical prompt. The
default policy file for an app might require prompting, but is it
easy to add a admin defined policy override. The separation of app
logic from the authentication policy also makes it easy to provide
different ways of prompting, whether graphical, or command line based,
or totally disabled.

|: 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 :|

reply via email to

[Prev in Thread] Current Thread [Next in Thread]