System Security Services Daemon

Edit Package sssd
https://pagure.io/SSSD/sssd

Provides a set of daemons to manage access to remote directories and
authentication mechanisms. It provides an NSS and PAM interface toward
the system and a pluggable backend system to connect to multiple different
account sources. It is also the basis to provide client auditing and policy
services for projects like FreeIPA.

Refresh
Refresh
Source Files (show merged sources derived from linked package)
Filename Size Changed
baselibs.conf 0000000222 222 Bytes
harden_sssd-ifp.service.patch 0000000778 778 Bytes
harden_sssd-kcm.service.patch 0000000855 855 Bytes
krb-noversion.diff 0000000712 712 Bytes
sssd-2.9.5.tar.gz 0008001964 7.63 MB
sssd-2.9.5.tar.gz.asc 0000000833 833 Bytes
sssd.changes 0000096560 94.3 KB
sssd.keyring 0000004694 4.58 KB
sssd.spec 0000026236 25.6 KB
symvers.patch 0000005599 5.47 KB
Comments 7

Ralf Kölmel's avatar

Will the build problem for Leap 15.1 or Leap 15.2 because of a not sufficient p11-kit version solved ? It would be also interesting if a sssd-kcm package (available since version 1.16) could be built for the new sssd release. Thanks for your infos !


Jan Engelhardt's avatar

Not from my side. Yes.


Ralf Kölmel's avatar

Thank you for the fast response and the building of the sssd-kcm package !


Michael Gumsley's avatar

Is there a timeline for when 2.6.3 will be submitted to factory? Particularly, it addresses a major regression in AD authentication introduced in 2.6.2.


Jan Engelhardt's avatar

whenever they get their signature file right :-/


Samuel Cabrero's avatar

https://github.com/SSSD/sssd/releases/download/2.6.3/sssd-2.6.3.tar.gz.asc seems to be fine. But 2.6.3 release tarball is signed by Pavel's key and sssd.keyring only contains Alexey's key.

@jengelh, do you agree to add both keys to the keyring?


Georg Pfuetzenreuter's avatar

Hi! Are there any objections to adding --with-subid to the build options to enable support for https://github.com/SSSD/sssd/commit/f546088226872f24722bdd94388816792bd5891a ? If I am not mistaken, our version of shadow (v4.11.1) should already include support for it, as per https://github.com/shadow-maint/shadow/commit/8492dee6632e340dee76eee895c3e30877bebf45.

openSUSE Build Service is sponsored by