News for hackers. Stuff that matters.

A comment on Systemd Inhibitor Locks Deep Dive. Parent comment

Re:Systemd Inhibitor Locks Deep Dive by kingosticks on Sunday April 11, 2021 @11:00AM (#26770761)
> If you don't really care about the security aspect it would be just as easy to tell the user to grant you access to the dbus socket for their session bus,

Do you have any more details about this? Doesn't dbus complain about that? Is this something more than changing the socket file permissions. Last time I tried to access the user session bus from something outside the session I ran into this kludge https://serverfault.com/questions/892465/starting-systemd-se...

I'm happy with the socket solution because it's got the security level I want (anyone on the local machine with local access to the socket file is fine) and I can really, really easily build whatever I want on top of it or plug it into whatever library because it's a simple socket. I want to use dbus, it seems the Right Way but it always seems to throw up road blocks.

[ Parent | on HN ]
Re:Systemd Inhibitor Locks Deep Dive by taway098123 on Sunday April 11, 2021 @12:40PM (#26771613)
Dbus won't allow it because you have to switch to that user before it lets you connect. You would have to have whatever is doing the access running as root and then change its user. There's not really any magic here, it's just a socket with access controls on it, the same thing you would be building anyway.
[ Parent | on HN ]