sssd_krb5_locator_plugin.so is not loaded (installed at wrong path)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| sssd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Xenial |
Fix Released
|
Medium
|
Andreas Hasenack | ||
Bug Description
[Impact]
Users cannot rely on the sssd krb5 locator plugin. Effect varies from slow logins (client trying to reach many different KDCs instead of directly the one specified by sssd configuration) to failed logins.
The bug is simple, and so is the fix. The plugin was installed in the wrong directory.
[Test Case]
This test case does not reproduce the exact scenario reported by the user, but is good enough to prove that the plugin is not loaded in the broken package, and is loaded just fine in the fixed package.
* install the packages on a xenial system. I suggest using LXD:
$ sudo apt install sssd krb5-kdc krb5-admin-server libpam-sss
For the kerberos prompts, answer:
- default kerberos realm: EXAMPLE.COM
- kerberos servers: just hit enter
- administrative server: just hit enter
* create the EXAMPLE.COM realm. Use any password during the creation, it doesn't matter:
$ sudo krb5_newrealm
* create the ubuntu principal in the EXAMPLE.COM realm with a password of "ubuntu". Note: please make sure your local ubuntu user uses a different password, or has none at all. When we login succesfully later, we want to be sure it was via kerberos, and not the local user.
$ sudo kadmin.local -q "addprinc -pw ubuntu <email address hidden>"
* configure the krb5 libraries to use a fake realm by default
- edit /etc/krb5.conf
- replace the default_realm value in [libdefaults] with LOCALHOST (just so it fails quickly):
[libdefaults]
default_realm = LOCALHOST
- do not restart the kerberos services
* Create the sssd configuration file /etc/sssd/sssd.conf with these contents:
"""
[sssd]
config_file_version = 2
services = pam
domains = kerberos.
[pam]
[domain/
id_provider = proxy
proxy_lib_name = files
auth_provider = krb5
krb5_server = YOURADDRESS
krb5_realm = EXAMPLE.COM
"""
- replace YOURADDRESS with the IP of your test container or VM (do not use 127.0.0.1)
- IMPORTANT: sudo chmod 0600 /etc/sssd/sssd.conf
* Start sssd:
$ sudo systemctl start sssd.service
* in one terminal:
$ tail -f /var/log/syslog
* in another terminal, run:
$ sudo login (or just become root and run login)
* attempt to login as ubuntu with the kerberos password created earlier "ubuntu"):
$ sudo login
xenial-
Password:
Login incorrect
* observe that syslog complains about not finding the the KDC for the EXAMPLE.COM realm:
Jul 21 21:03:40 xenial-
* /var/log/auth will report a general PAM error with no specifics
* install the fixed packages from proposed
* retry the login as ubuntu:
- login succeeds
- no errors in /var/log/syslog
- /var/log/auth will report a good login via pam_sss
* run klist to verify you have the kerberos tgt:
$ klist
Ticket cache: FILE:/tmp/
Default principal: <email address hidden>
Valid starting Expires Service principal
07/21/2017 21:05:26 07/22/2017 07:05:26 <email address hidden>
renew until 07/22/2017 21:05:26
- run kdestroy followed by kinit to verify you will NOT get the tgt, because /etc/krb5.conf is still specifying the incorrect realm:
$ kdestroy
$ kinit
kinit: Cannot find KDC for realm "LOCALHOST" while getting initial credentials
This proves that the krb5 locator sssd plugin was loaded and worked, because it found the right realm and its KDC via the sssd configuration only.
[Regression Potential]
The fix is just placing the plugin in the correct directory. Users have already been using a workaround of symlinking the file, or even copying it manually over to the right place.
The directory where the plugin was located, and where it is located now, is private, and no other packages will be loading it other than SSSD. So changing its location should not affect other software installed on the system.
[Other Info]
None at this time.
| Michael Smith (mzs) wrote Dependencies.txt | #1 |
| description: | updated |
| tags: | added: apport-collected uec-images xenial |
| description: | updated |
| Timo Aaltonen (tjaalton) wrote | #2 |
| Changed in sssd (Ubuntu): | |
| status: | New → Fix Committed |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in sssd (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| David Flynn (davidf+launchpad-net) wrote | #4 |
| tags: | added: server-next |
| Andreas Hasenack (ahasenack) wrote | #5 |
| Changed in sssd (Ubuntu Xenial): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Andreas Hasenack (ahasenack) |
| Changed in sssd (Ubuntu Xenial): | |
| status: | Confirmed → In Progress |
| description: | updated |
| description: | updated |
| Christian Ehrhardt (paelzer) wrote | #6 |
| Andreas Hasenack (ahasenack) wrote | #7 |
| Brian Murray (brian-murray) wrote Please test proposed package | #8 |
| Changed in sssd (Ubuntu Xenial): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed verification-needed-xenial |
| Andreas Hasenack (ahasenack) wrote | #9 |
| tags: |
added: verification-done-xenial removed: verification-needed-xenial |
| Launchpad Janitor (janitor) wrote | #10 |
| Changed in sssd (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Łukasz Zemczak (sil2100) wrote Update Released | #11 |
apport information