-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A bunch of assorted patches related to socket activation feature (part 1) #6873
Commits on Sep 4, 2023
-
Get rid of '--dbus-activated'.
Code makes no difference handling '--socket-activated' and '--dbus-activated', it only makes things more obscure. Moreover, on a systemd enabled system, dbus activation actually starts systemd service anyway, so there is really no big difference.
Configuration menu - View commit details
-
Copy full SHA for 39fe549 - Browse repository at this point
Copy the full SHA 39fe549View commit details -
Configuration menu - View commit details
-
Copy full SHA for e36d10f - Browse repository at this point
Copy the full SHA e36d10fView commit details -
CONF: there is no use for CONFDB_FALLBACK_CONFIG
since implicit files provider can't be enabled by default anymore. Resolves: SSSD#5022
Configuration menu - View commit details
-
Copy full SHA for 3ba2054 - Browse repository at this point
Copy the full SHA 3ba2054View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2de10f7 - Browse repository at this point
Copy the full SHA 2de10f7View commit details -
Configuration menu - View commit details
-
Copy full SHA for e5e3726 - Browse repository at this point
Copy the full SHA e5e3726View commit details -
SYSTEMD: removed unneeded capabilities
This patch removes capabilities that aren't needed at all. Some (if not all) of remaining capabilities can be probably avoided with proper code changes, but currently those are needed. Examples (not limiting) of those caps usage: - CAP_DAC_OVERRIDE (@additional_caps@): access to /var/log/sssd, to /var/lib/sss/pipes/private/* (sssd:sssd owned sbus-monitor/dp sbus sockets) - CAP_CHOWN: `chown_debug_file()` in case of monitor activation - CAP_SETUID/CAP_SETGID: drop privs in case of monitor activation, switch_creds (in particular, sssd_kcm executing krb5_child for ticket renewal) - CAP_FOWNER: chmod(mem-cache) It's not that clear about 'CAP_KILL'. When 'sssd_be' terminates child process, it either still runs under root (so uid matches and no caps needed) or it dropped privs already and have lost CAP_KILL anyway. Another thing is 'monitor' signalling responders and providers that could be running under 'sssd' while 'monitor' itself runs under 'root'.
Configuration menu - View commit details
-
Copy full SHA for 6f0fd67 - Browse repository at this point
Copy the full SHA 6f0fd67View commit details -
SYSV/NSS: avoid chmod() in sssd_nss
This allows to remove CAP_FOWNER.
Configuration menu - View commit details
-
Copy full SHA for c5b51d7 - Browse repository at this point
Copy the full SHA c5b51d7View commit details -
SYSTEMD::IFP: don't restrict ExecStartPre=chown(log)
'PermissionsStartOnly' is deprecated but used for consistency with other unit files.
Configuration menu - View commit details
-
Copy full SHA for f1b7d2b - Browse repository at this point
Copy the full SHA f1b7d2bView commit details -
Configuration menu - View commit details
-
Copy full SHA for dd24e1f - Browse repository at this point
Copy the full SHA dd24e1fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 944a633 - Browse repository at this point
Copy the full SHA 944a633View commit details