Bug 1725168
| Summary: | sssd-proxy crashes resolving groups with no members | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jakub Hrozek <jhrozek> |
| Component: | sssd | Assignee: | SSSD Maintainers <sssd-maint> |
| Status: | CLOSED ERRATA | QA Contact: | sssd-qe <sssd-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.1 | CC: | abokovoy, extras-qa, grajaiya, gwync, jhrozek, lslebodn, mniranja, mzidek, pbrezina, rharwood, sbose, sgoveas, ssorce, tscherf |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | sssd-2.2.0-3.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1724717 | Environment: | |
| Last Closed: | 2019-11-05 22:34:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1724717 | ||
| Bug Blocks: | |||
|
Description
Jakub Hrozek
2019-06-28 14:58:40 UTC
* master: e1b678c0cce73494d986610920b03956c1dbb62a To reproduce, set up a domain like this: id_provider = proxy proxy_lib_name = files enumerate = true ignore_group_members = False debug_level=9 then run "id $user" for a user from passwd, sssd_be will crash resolving the primary group of the user.
Reproducer:
===========
Version:
libsss_nss_idmap-2.2.0-1.el8.x86_64
sssd-winbind-idmap-2.2.0-1.el8.x86_64
sssd-nfs-idmap-2.2.0-1.el8.x86_64
sssd-krb5-common-2.2.0-1.el8.x86_64
sssd-ipa-2.2.0-1.el8.x86_64
sssd-tools-2.2.0-1.el8.x86_64
sssd-polkit-rules-2.2.0-1.el8.x86_64
libsss_idmap-2.2.0-1.el8.x86_64
python3-sssdconfig-2.2.0-1.el8.noarch
sssd-libwbclient-2.2.0-1.el8.x86_64
libsss_autofs-2.2.0-1.el8.x86_64
sssd-common-2.2.0-1.el8.x86_64
sssd-common-pac-2.2.0-1.el8.x86_64
sssd-ad-2.2.0-1.el8.x86_64
sssd-krb5-2.2.0-1.el8.x86_64
python3-sss-2.2.0-1.el8.x86_64
sssd-2.2.0-1.el8.x86_64
sssd-kcm-2.2.0-1.el8.x86_64
sssd-proxy-2.2.0-1.el8.x86_64
libsss_certmap-2.2.0-1.el8.x86_64
sssd-client-2.2.0-1.el8.x86_64
libsss_sudo-2.2.0-1.el8.x86_64
sssd-dbus-2.2.0-1.el8.x86_64
sssd-ldap-2.2.0-1.el8.x86_64
libsss_simpleifp-2.2.0-1.el8.x86_64
1. Setup a kerber server
2. Add a user test1 in kerberos database
3. Create a local user (/etc/passswd) test1
4. Configure sssd.conf as below:
$ Cat /etc/sssd/sssd.conf
[sssd]
services = nss, pam
domains = LOCAL
[nss]
homedir_substring = /home
[domain/LOCAL]
id_provider = proxy
proxy_lib_name = files
enumerate = true
ignore_group_members = False
debug_level=9
cache_credentials = True
auth_provider = krb5
krb5_server = ci-vm-10-0-144-177.hosted.upshift.rdu2.redhat.com
krb5_realm = EXAMPLE.TEST
krb5_validate = true
5. Restart sssd
6. issue command: "id test1"
sssd_be crashes:
Aug 02 09:43:31 ci-vm-10-0-144-177.hosted.upshift.rdu2.redhat.com sssd[be[LOCAL]][26786]: Starting up
Aug 02 09:43:31 ci-vm-10-0-144-177.hosted.upshift.rdu2.redhat.com systemd-coredump[26785]: Process 26779 (sssd_be) of user 0 dumped core.
Stack trace of thread 26779:
#0 0x00007fb4f8519f5b save_group (libsss_proxy.so)
#1 0x00007fb4f851a9f3 get_gr_gid.isra.4 (libsss_proxy.so)
#2 0x00007fb4f851b742 proxy_account_info_handler_send (libsss_proxy.so)
#3 0x00005643f54c6e6c dp_req_send (sssd_be)
#4 0x00005643f54c9b6e dp_get_account_info_send (sssd_be)
#5 0x00007fb50dfb3a52 _sbus_sss_invoke_in_uusss_out_qus_step (libsss_iface.so)
#6 0x00007fb50d95a279 tevent_common_invoke_timer_handler (libtevent.so.0)
#7 0x00007fb50d95a41e tevent_common_loop_timer_delay (libtevent.so.0)
#8 0x00007fb50d95b959 epoll_event_loop_once (libtevent.so.0)
#9 0x00007fb50d95985b std_event_loop_once (libtevent.so.0)
#10 0x00007fb50d954a55 _tevent_loop_once (libtevent.so.0)
#11 0x00007fb50d954cfb tevent_common_loop_wait (libtevent.so.0)
#12 0x00007fb50d9597eb std_event_loop_wait (libtevent.so.0)
#13 0x00007fb5108e7ec7 server_loop (libsss_util.so)
#14 0x00005643f54b93bb main (sssd_be)
#15 0x00007fb50ce2c873 __libc_start_main (libc.so.6)
#16 0x00005643f54b957e _start (sssd_be)
7. Update sssd to 2.2.0-5
[root@ci-vm-10-0-144-177 packages]# rpm -qa | grep sss
libsss_nss_idmap-2.2.0-1.el8.x86_64
sssd-winbind-idmap-2.2.0-1.el8.x86_64
sssd-nfs-idmap-2.2.0-1.el8.x86_64
sssd-client-2.2.0-5.el8.x86_64
sssd-dbus-2.2.0-5.el8.x86_64
python3-sss-2.2.0-5.el8.x86_64
sssd-2.2.0-5.el8.x86_64
sssd-polkit-rules-2.2.0-5.el8.x86_64
sssd-libwbclient-2.2.0-1.el8.x86_64
libsss_autofs-2.2.0-1.el8.x86_64
python3-sssdconfig-2.2.0-5.el8.noarch
sssd-common-2.2.0-5.el8.x86_64
sssd-common-pac-2.2.0-5.el8.x86_64
sssd-ad-2.2.0-5.el8.x86_64
sssd-ldap-2.2.0-5.el8.x86_64
sssd-proxy-2.2.0-5.el8.x86_64
sssd-ipa-2.2.0-5.el8.x86_64
sssd-tools-2.2.0-5.el8.x86_64
sssd-kcm-2.2.0-5.el8.x86_64
libsss_certmap-2.2.0-1.el8.x86_64
libsss_sudo-2.2.0-1.el8.x86_64
libsss_idmap-2.2.0-5.el8.x86_64
sssd-krb5-common-2.2.0-5.el8.x86_64
sssd-krb5-2.2.0-5.el8.x86_64
libsss_simpleifp-2.2.0-5.el8.x86_64
[root@ci-vm-10-0-144-177 packages]#
8. Run id test1
$
[root@ci-vm-10-0-144-177 packages]# ps -ef | grep sssd
root 27738 1 0 09:47 ? 00:00:00 /usr/sbin/sssd -i --logger=files
root 27740 27738 0 09:47 ? 00:00:00 /usr/libexec/sssd/sssd_be --domain LOCAL --uid 0 --gid 0 --logger=files
root 27741 27738 0 09:47 ? 00:00:00 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
root 27742 27738 0 09:47 ? 00:00:00 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files
root 27746 24466 0 09:47 pts/1 00:00:00 grep --color=auto sssd
[root@ci-vm-10-0-144-177 packages]#
9. sssd doesn't crash. when id test1 user is run.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3651 |