On 01/21/2015 01:54 PM, Roland Mainz wrote:
sssd and sssd_be. I've got all the logs and straces and whatever. Basically,
it seems D-Bus is trying to store its keyring in ~/.dbus-keyrings directory.
With user being root it naturally tries to store it in /root/.dbus-keyrings.
Actually, as we have control of passswd database, we can put root's home
anywhere. I'll try that.
Erm... isn't that risky ? Other applications running as user "root" in
parallel to what you're doing might trip over such a change...
No, we have the NSS module and passwd file location overridden with
nss_wrapper for our test only. We're also running as a regular user, so we
can't really change /etc/passwd.
... is there no way to override the keyring location (quick look at
|dbus_keyring_new_homedir()| doesn't show any way... but maybe one of the
DBus experts might know a way. If this fails there is always
/proc/$pid/root/ which can AFAIK be overridden on a per-process basis
(details on demand, I have to dig out how this works...)) ?
Yes, I looked at the code as well and couldn't find any way to change that.
Changing filesystem root would also require root privelegies and we don't
have that. And then we don't want to haul the whole hierarchy that various
programs we invoke might require.
Nick
_______________________________________________
sssd-devel mailing list
sssd-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-devel
