Cockpit, OpenLMI, and others want to use the systemd D-Bus API to manage
system services/sockets etc. In addition we use polkit to authorize
users and allow people to escalate privileges as needed.
It seems that the D-Bus API of systemd doesn't support polkit:
On Tue, 15.07.14 13:35, Stef Walter (s...@thewalter.net) wrote:
Cockpit, OpenLMI, and others want to use the systemd D-Bus API to manage
system services/sockets etc. In addition we use polkit to authorize
users and allow people to escalate privileges as needed.
It seems that the D-Bus API
On 07/15/2014 03:15 PM, Lennart Poettering wrote:
On Tue, 15.07.14 13:35, Stef Walter (s...@thewalter.net) wrote:
Cockpit, OpenLMI, and others want to use the systemd D-Bus API to manage
system services/sockets etc. In addition we use polkit to authorize
users and allow people to escalate
On 15.07.2014 15:15, Lennart Poettering wrote:
On Tue, 15.07.14 13:35, Stef Walter (s...@thewalter.net) wrote:
Cockpit, OpenLMI, and others want to use the systemd D-Bus API to manage
system services/sockets etc. In addition we use polkit to authorize
users and allow people to escalate
On 07/15/2014 03:38 PM, Stef Walter wrote:
Not sure about:
* Halt(), PowerOff(), Reboot()
OpenLMI is interested in these. They are already covered by logind,
which is integrated with polkit just fine. Look for actions like
org.freedesktop.login1.reboot, reboot-multiple-sessions etc. in
On 15.07.2014 15:46, Jan Safranek wrote:
On 07/15/2014 03:38 PM, Stef Walter wrote:
Not sure about:
* Halt(), PowerOff(), Reboot()
OpenLMI is interested in these. They are already covered by logind,
which is integrated with polkit just fine. Look for actions like
