These are only examples, for a few very common actions. You are expected to write your own rules for the rest. The syntax is regular JavaScript, but see the polkit(8)
manpage for the object structure and available API. These examples are for polkit versions 106 and later, with the JS interpreter. They won't work with Debian's polkit v105.
-
If you don't know the action name, run
pkaction
:pkaction | grep cups
-
The possible results are
YES
,AUTH_SELF(_KEEP)
,AUTH_ADMIN(_KEEP)
,NO
. Returning a result is final. Returningnull
will continue checking other rules. -
Put your rules in
/etc/polkit-1/rules.d/*.rules
. (You can check everything in one giant addRule, or you can have a separate file and separate addRule for each program; it doesn't matter.) -
To test your rules, use
pkcheck
:pkcheck -u -p $$ -a org.freedesktop.packagekit.upgrade-system
Is there possibility to ".test()" on a "action.lookup("XYZ")" result? or convert/use another function like indexOf on an action-lookup result?