at a hardened system I do get : Dec 20 16:27:50 t44 kernel: grsec: time set by /usr/bin/tlsdate-helper[tlsdate-helper:4227] uid/euid:0/0 gid/egid:0/0, parent /lib64/rc/sh/runscript.sh[runscript.sh:4214] uid/euid:0/0 gid/egid:0/0 Dec 20 18:10:43 t44 tlsdated[4290]: [dbus] failed to get name: Connection ":1.40" is not allowed to own the service "org.torproject.tlsdate" due to security policies in the configuration file Dec 20 18:10:43 t44 tlsdated[4290]: Failed to initialize DBus Dec 20 18:10:43 t44 tlsdated[4290]: tlsdated clean up finished; exiting!
I got this on a regular Gentoo system with tlsdate version 0.0.12 ebuild installed, when attempting to start the tlsdated daemon, using: service tlsdated start An excerpt from my messages log: Dec 21 13:42:02 sapientia /etc/init.d/tlsdated[31969]: status: crashed Dec 21 13:42:04 sapientia /etc/init.d/tlsdated[31974]: WARNING: tlsdated has already been started Dec 21 13:42:08 sapientia /etc/init.d/tlsdated[32172]: start-stop-daemon: no matching processes found Dec 21 13:42:14 sapientia tlsdated[32214]: [dbus] failed to get name: Connection ":1.30" is not allowed to own the service "org.to rproject.tlsdate" due to security policies in the configuration file Dec 21 13:42:14 sapientia tlsdated[32214]: Failed to initialize DBus Dec 21 13:42:14 sapientia tlsdated[32214]: tlsdated clean up finished; exiting!
BTW: as a workaround I disabled the dbus use flag for net-misc/tlsdate 0.0.12
Previous versions failed to install the dbus config, this should be fixed in 0.0.12-r1