Blame SOURCES/0038-SUDO-Root-should-be-able-to-read-write-sssd-sudo-soc.patch

ca1eb8
From 2708fb488277209a60a5daf5217502c029c196c1 Mon Sep 17 00:00:00 2001
ca1eb8
From: Lukas Slebodnik <lslebodn@redhat.com>
ca1eb8
Date: Tue, 24 Jul 2018 18:52:08 +0000
ca1eb8
Subject: [PATCH] SUDO: Root should be able to read/write sssd-sudo socket
ca1eb8
ca1eb8
There is not any reason to require additional capabilities from root
ca1eb8
when sssd is running as unprivileged user.
ca1eb8
ca1eb8
Sudo UNIX socket is not a real private socket. It just cannot
ca1eb8
be used by others. Just owner(sssd) and root should be able to use it.
ca1eb8
ca1eb8
Resolves:
ca1eb8
https://pagure.io/SSSD/sssd/issue/3778
ca1eb8
ca1eb8
Merges: https://pagure.io/SSSD/sssd/pull-request/3784
ca1eb8
ca1eb8
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
ca1eb8
(cherry picked from commit 21ea8204a0bd8ea4451f420713e909d3cfee34ef)
ca1eb8
---
ca1eb8
 src/sysv/systemd/sssd-sudo.socket.in | 3 +--
ca1eb8
 1 file changed, 1 insertion(+), 2 deletions(-)
ca1eb8
ca1eb8
diff --git a/src/sysv/systemd/sssd-sudo.socket.in b/src/sysv/systemd/sssd-sudo.socket.in
ca1eb8
index 96a8b0327ddb4d331c9b2e97ece3453f8f76872d..e94a2f6151e3d69edc304776b72a81db22762503 100644
ca1eb8
--- a/src/sysv/systemd/sssd-sudo.socket.in
ca1eb8
+++ b/src/sysv/systemd/sssd-sudo.socket.in
ca1eb8
@@ -10,8 +10,7 @@ Conflicts=shutdown.target
ca1eb8
 ExecStartPre=@libexecdir@/sssd/sssd_check_socket_activated_responders -r sudo
ca1eb8
 ListenStream=@pipepath@/sudo
ca1eb8
 SocketUser=@SSSD_USER@
ca1eb8
-SocketGroup=@SSSD_USER@
ca1eb8
-SocketMode=0600
ca1eb8
+SocketMode=0660
ca1eb8
 
ca1eb8
 [Install]
ca1eb8
 WantedBy=sssd.service
ca1eb8
-- 
ca1eb8
2.14.4
ca1eb8