diff options
| author | Fabiano Fidêncio <fidencio@redhat.com> | 2017-03-13 17:06:04 +0100 |
|---|---|---|
| committer | Lukas Slebodnik <lslebodn@redhat.com> | 2017-03-15 16:01:34 +0100 |
| commit | b7430c4f4b98efe08d9d13d202fbb76229628b30 (patch) | |
| tree | d2fdce8ea8457f0778bce3cc4e190a2329f3fb51 /src/python | |
| parent | ed2a5dad1ec82eda8a43ed8b0a05a6b01c3a6586 (diff) | |
| download | sssd-b7430c4f4b98efe08d9d13d202fbb76229628b30.tar.gz sssd-b7430c4f4b98efe08d9d13d202fbb76229628b30.tar.xz sssd-b7430c4f4b98efe08d9d13d202fbb76229628b30.zip | |
NSS: Don't set SocketUser/SocketGroup as "sssd" in sssd-nss.socket
NSS service is always run as root, so there's no need to change its
socket ownership to the sssd user.
More than that, by setting up the SocketUser and SocketGroup to "sssd"
a loop would be caused as the "sssd" would trigger an initgroups call
during the NSS socket setup.
The problem was found when starting up a machine with SSSD built with
"--with-sssd-user=sssd" and having "sss" before "files" in the
name-service switch.
Related:
https://pagure.io/SSSD/sssd/issue/3322
Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com>
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com>
Diffstat (limited to 'src/python')
0 files changed, 0 insertions, 0 deletions