On Fri, May 29, 2015 at 11:05 AM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
On May 28, 2015 2:28 PM, aaron_wri...@selinc.com wrote:
I'm working on an embedded system, and I ran into a situation where
a non-root user needs to runs systemctl, but when I try I get:
~ $ systemctl status
On 29 May 2015 at 01:21, aaron_wri...@selinc.com wrote:
Brandon Philips bran...@ifup.co wrote on 05/28/2015 05:10:33 PM:
Access to the system dbus is controlled by dbus policies. You will
need to write a policy for giving this user access to the systemd1 object.
I compiled systemd without
On Fri, May 29, 2015 at 10:23 AM, Andrei Borzenkov arvidj...@gmail.com wrote:
On Fri, May 29, 2015 at 11:05 AM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
On May 28, 2015 2:28 PM, aaron_wri...@selinc.com wrote:
I'm working on an embedded system, and I ran into a situation where
a
On 05/29/2015 05:26 AM, Andrei Borzenkov wrote:
If you do not use D-Bus daemon systemd will be listening on private
socket. In this case the only check it does is that peer runs as UID=0
(note - not EUID, so suid does not really help).
I wonder how access control is implemented in kdbus
On Fri, 29.05.15 10:54, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
On Fri, May 29, 2015 at 10:23 AM, Andrei Borzenkov arvidj...@gmail.com
wrote:
On Fri, May 29, 2015 at 11:05 AM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
On May 28, 2015 2:28 PM, aaron_wri...@selinc.com
On Thu, 28.05.15 17:21, aaron_wri...@selinc.com (aaron_wri...@selinc.com) wrote:
Brandon Philips bran...@ifup.co wrote on 05/28/2015 05:10:33 PM:
Access to the system dbus is controlled by dbus policies. You will
need to write a policy for giving this user access to the systemd1
object.
On Fri, May 29, 2015 at 1:02 PM, Lennart Poettering lenn...@poettering.net
wrote:
On Thu, 28.05.15 17:21, aaron_wri...@selinc.com (aaron_wri...@selinc.com)
wrote:
Brandon Philips bran...@ifup.co wrote on 05/28/2015 05:10:33 PM:
Access to the system dbus is controlled by dbus policies. You
On Fri, 29.05.15 13:56, Mantas Mikulėnas (graw...@gmail.com) wrote:
systemd will always use D-Bus (the protocol) for IPC, that's not
optional, and you cannot turn it off neither during build-time nor
during runtime. systemd does not use libdbus to implement this
however, but instead it
I compiled systemd without dbus support (--disable-dbus), and there is
no
dbus daemon or dbus lib on the system. Is that a requirement to get
the
functionality I want? I didn't see much need for dbus as the system
works
quite well without it. Well, except for this of course.
Brandon Philips bran...@ifup.co wrote on 05/28/2015 05:10:33 PM:
Access to the system dbus is controlled by dbus policies. You will
need to write a policy for giving this user access to the systemd1
object.
I compiled systemd without dbus support (--disable-dbus), and there is no
dbus
On Thu, May 28, 2015 at 9:21 PM, aaron_wri...@selinc.com wrote:
Brandon Philips bran...@ifup.co wrote on 05/28/2015 05:10:33 PM:
Access to the system dbus is controlled by dbus policies. You will
need to write a policy for giving this user access to the systemd1 object.
I compiled systemd
Access to the system dbus is controlled by dbus policies. You will need to
write a policy for giving this user access to the systemd1 object.
On May 28, 2015 2:28 PM, aaron_wri...@selinc.com wrote:
I'm working on an embedded system, and I ran into a situation where a
non-root user needs to runs
В Thu, 28 May 2015 17:21:14 -0700
aaron_wri...@selinc.com пишет:
Brandon Philips bran...@ifup.co wrote on 05/28/2015 05:10:33 PM:
Access to the system dbus is controlled by dbus policies. You will
need to write a policy for giving this user access to the systemd1
object.
I compiled
13 matches
Mail list logo
