Consistent PolicyKit system policy

[Tim Waugh]

When defining a new policy mechanism for PolicyKit, what are the "rules"
for setting the default policy?  PolicyKit's flexibility is excellent,
but it means that we have to choose sensible and consistent defaults for
each application that uses it.

I ask because the default policy for cups-pk-helper is to require the
root password, and not to remember it even for that session.

What is the goal of the default Fedora PolicyKit policy system-wide, and
how can we check that PolicyKit mechanisms' default policies are
adhering to it?

For example, what should the default Fedora policy be for locally
connected peripherals?

Tim.
*/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20090810/a2d4dff7/attachment.sig>