Bug 1132049 - libldb1 security update breaks sssd
libldb1 security update breaks sssd
Status: RESOLVED DUPLICATE of bug 1131686
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Other
Leap 15.0
x86-64 Other
: P5 - None : Major (vote)
: ---
Assigned To: James McDonough
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2019-04-10 07:22 UTC by Samu Voutilainen
Modified: 2019-04-10 14:47 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Samu Voutilainen 2019-04-10 07:22:12 UTC
User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0
Build Identifier: 


Sorry if this is a duplicate (the search doesn’t seem to work now), but sssd package has a compatibility issue with new libldb1 security update.

When libldb1 got the new update (ldb-1.2.4-lp150.10.1.src), I guess it changed the ABI and someone decided to bump the SO version, without bumping actual package version. sssd has kind of hidden dependency to ldb, which enforces ldb version to be a specific version (it was compiled against). 

With updates packages, it just outputs following data:

systemd[1]: sssd.service: Control process exited, code=exited status=4
sssd[8820]: SSSD couldn't load the configuration database [5]: Input/output error.
sssd[8820]: ldb: failed to initialise module /usr/lib64/ldb/samba : Unavailable
yurie sssd[8820]: ldb: failed to initialise module /usr/lib64/ldb/samba/acl.so : Unavailable
sssd[8820]: ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.2.4 module_version=1.2.3
systemd[1]: Starting System Security Services Daemon...

I think the package needs to be bumped properly given the actual SO version has been bumped.

Also, I don’t know if sssd’s package already does it, but maybe it should enforce that the version it was built against it gets installed, instead of just having any version.

Reproducible: Always

Steps to Reproduce:
1. Update to newest version
2. Restart sssd
Actual Results:  
The errors specified above.

Expected Results:  
That the software actually worked.
Comment 1 Marcus Meissner 2019-04-10 14:47:22 UTC
fix was released today morning.

your bug had 4 dups

*** This bug has been marked as a duplicate of bug 1131686 ***