April 2024 - Sssd-maintainers - Fedora mailing-lists

[Bug 1886841] New: Pinpad card reader for login authentication yet you are asked also enter pin on pc keyboard
by bugzilla＠redhat.com 08 Nov '24

08 Nov '24

https://bugzilla.redhat.com/show_bug.cgi?id=1886841 Bug ID: 1886841 Summary: Pinpad card reader for login authentication yet you are asked also enter pin on pc keyboard Product: Fedora Version: 32 Hardware: x86_64 URL: https://lists.fedoraproject.org/archives/list/freeipa- users(a)lists.fedorahosted.org/thread/FLLIA5RLHT3MO4NI2F 3MJNMBBNGGZA4Z/ OS: Linux Status: NEW Component: sssd Severity: high Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: peter(a)unix-edu.se QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, jhrozek(a)redhat.com, lslebodn(a)redhat.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, rharwood(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: Hello Folks! We are working on getting smart card authentication working using pinpad card readers for improved security. To do this we use: FreeIPA Server is running on Fedora 32 with latest updates. FreeIPA Clients is Fedora 32 Workstation installed on pc with latest updates with connected usb card reader. The card reader is Gemalto CT700 with pinpad, we use several user individual SmartCard HSM 4K with FreeIPA signed certificates on them. FreeIPA Clients run OpenSC and are configured to use smartcard certificate based authentication, setup per Smartare HSM best practice. Further clients are using SSSD and not PAM_PKCS#11. All working great using smartcard for authentication, as long not enabling the pinpad in opensc. If doing so we are prompted for the PIN not only in the pinpad reader but also GDM prompts you to enter PIN on keyboard. Expected result is to be logged in directly after entering correct PIN code on pinpad reader, not being prompted by GDM to enter PIN on keyboard as well. If enabling pinpad in opensc, login gets a bit odd: 1. Fedora 32 Workstation GDM menu prompts a few users that can login. 2. Smartcard is inserted in reader. 3. GDM blanks out the screen and smartcard reader prompts to enter PIN in its lcd display. 4. Entering pin on smartcard reader followed by pressing ok button on smartcard reader at getting result Pin OK in reader display. 5. GDM now prompts for entering PIN on keyboard, this is unexpected, instead of directly being logged in to the window manager, here Gnome (or xfce, whatever window manager you selected to use). 6. You have to enter the PIN now on keyboard, followed by hitting enter. 7. Once again smartcard reader now prompts for PIN in its lcd display. 8. Entering PIN on the smartcard pinpad reader followed by pressing pinpad ok button. 9. You are now logged in, and all is normal. If ripping out the smartcard from reader the screen locks, as expected. Sometimes, but not always, you are logged in to window manager directly after step 5. What could this be, anyone who have seen this before or know how to set it up ? Reproducible: Always Steps to Reproduce: 1. Install and setup FreeIPA server and client on Fedora32 latest updates to use smartcard authentication for login. Work on IPA Server: ------------------- Install Fedora 32 server minimal installation all excluded, update to latest version (dnf update -y), set hostname, enter server hostname (ipaserver.mydomain.com) and ip in /etc/hosts, enable and start chrony, reboot. (As root user) dnf install ipa-server bind-dyndb-ldap ipa-server-dns -y for SERVICES in ntp http https ldap ldaps kerberos kpasswd dns; do firewall-cmd --permanent --add-service=$SERVICES; done ipa-server-install --setup-dns . . . Add one secondary DNS in /etc/NetworkManager/conf.d/zzz-ipa.conf klist kinit admin authselect select sssd with-sudo with-mkhomedir ipa user-add user3 --first=user3 --last=test --email=user3(a)mydomain.com --shell=/bin/bash --password id user3 ipa user-find user3 ssh user3(a)ipaserver.mydomain.com (change password) reboot (As root user) klist kinit admin ipa-advise config-server-for-smart-card-auth > config-server-for-smart-card-auth.sh chmod u+x config-server-for-smart-card-auth.sh ./config-server-for-smart-card-auth.sh /etc/ipa/ca.crt . . reboot ipa-advise config-client-for-smart-card-auth > /tmp/config-client-for-smart-card-auth.sh chmod a+r /tmp/config-client-for-smart-card-auth.sh Work on Fedora 32 workstation: ------------------------------ Install Fedora 32 Workstation from live dvd to PC, update to latest version (dnf update -y), set hostname, enter server hostname (workstation.mydomain.com) and ip in /etc/hosts, enable and start chrony. change/add to /etc/sysconfig/network-scripts/reboot, so IPA server becomes primary DNS for the Fedora 32 Workstation: PEERDNS=no DNS1=<ipa server ip address> DNS2=<second dns server> SEARCH=mydomain.com DOMAIN=mydomain.com Then reboot Login and check that DNS is working. (as root user) dnf install freeipa-client.x86_64 -y ipa-client-install --mkhomedir id user3 reboot Connect gemalto CT700 card reader to pc/Fedora Workstation. lsusb dnf install opensc ccid pcsc-tools -y systemctl enable pcscd systemctl start pcscd scp user3@ipaserver:/tmp/config-client-for-smart-card-auth.sh . chmod +x config-client-for-smart-card-auth.sh ./config-client-for-smart-card-auth.sh /etc/ipa/ca.crt . . . In /etc/opensc.conf enable pinpad by uncommenting enable_pinpad = true; Ensure pam_cert_auth is true in sssd.conf: grep ^pam_cert_auth /etc/sssd/sssd.conf pam_cert_auth = True authselect select sssd with-mkhomedir with-sudo with-smartcard with-smartcard-lock-on-removal --force authselect current reboot 2. Prepare smartcard-hsm with user3 certificate using (as root user) kinit admin Insert smartcard-hsm in gemalto ct700 card reader! pcsc_scan Using reader plug'n play mechanism Scanning present readers... 0: Gemalto Ezio Shield (I<some number>) 00 00 Wed Sep 23 14:12:27 2020 Reader 0: Gemalto Ezio Shield (I<some number>) 00 00 . . . Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): <some hex number> Smartcard-HSM http://www.cardcontact.de/products/sc-hsm.html pensc-tool --list-readers # Detected readers (pcsc) Nr. Card Features Name 0 Yes PIN pad Gemalto Ezio Shield (I<some number>) 00 00 pkcs11-tool --list-slots Available slots: Slot 0 (0x0): Gemalto Ezio Shield (I<some number>) 00 00 token label : UserPIN (SmartCard-HSM) token manufacturer : www.CardContact.de token model : PKCS#15 emulated token flags : login required, PIN pad present, rng, token initialized, PIN initialized hardware version : 24.13 firmware version : 2.5 serial num : DECM<some number> pin min/max : 6/15 sc-hsm-tool --create-dkek-share dkek-share-1.pbe . . . sc-hsm-tool --initialize --so-pin <long pincode> --pin <pincode> --dkek-shares 1 sc-hsm-tool . . . DKEK shares : 1 DKEK import pending, 1 share(s) still missing sc-hsm-tool --import-dkek-share dkek-share-1.pbe . . . Enter password to decrypt DKEK share : <pincode> sc-hsm-tool . . . DKEK shares : 1 DKEK key check value : <some hex code> # generate keypair pkcs11-tool --module opensc-pkcs11.so --login --pin <pincode> --keypairgen --key-type rsa:2048 --id 10 --label "HSM RSA Key user3" pkcs11-tool --list-objects . . . pkcs11-tool --test --login --pin <pincode> . . . # Backup DKEK sc-hsm-tool --wrap-key wrap-key-1.bin --key-reference 1 --pin <pincode> # Extract card public key for slot 10 pkcs15-tool --read-public-key 10 > user3.pub # Prepping for and Create CSR to sign by IPA for user3 # Create a file hsm.conf with the content below cat hsm.conf # PKCS11 engine config openssl_conf = openssl_def [openssl_def] engines = engine_section [req] distinguished_name = req_distinguished_name [req_distinguished_name] # empty. [engine_section] pkcs11 = pkcs11_section [pkcs11_section] engine_id = pkcs11 PIN = init = 0 # Test that hsm.conf is working, and find pkcs11 engine OPENSSL_CONF=./hsm.conf openssl engine (rdrand) Intel RDRAND engine (dynamic) Dynamic engine loading support (pkcs11) pkcs11 engine # Create CSR to sign by IPA for user3 OPENSSL_CONF=./hsm.conf openssl req -engine pkcs11 -keyform engine -new -key 10 -sha256 -out user3.csr -subj "/CN=user3" Login to IPA server using the web interface https://ipaserver.mydomain.com (this can be performed from command line as well, but we did use the web interface to IPA) user user3 Actions -> new certificate select profile IECuserRoles copy "user3.csr" from above and paste it in and click "issue" (IPA now sign the CSR) To retrieve the signed certificate for user3: user user3 by Certificates click Actions -> Download and save as. (it downloads as cert.pem) Copy the downloaded cerificate (cert.pem) to host with card reader (Fedora 32 Workstation) Rename it: mv cert.pem user3.pem # convert to der format: openssl x509 -in user3.pem -out user3.der -outform der # write it to the card in slot 10 pkcs11-tool --module opensc-pkcs11.so --login --pin <pincode> --write-object user36.der --type cert --id 10 # check that it is there: pkcs11-tool --list-objects Using slot 0 with a present token (0x0) Certificate Object; type = X.509 cert label: Certificate subject: DN: O=MYDOMAIN.COM, CN=user3 ID: 10 Public Key Object; RSA 2048 bits label: Certificate ID: 10 Usage: encrypt, verify Smartcard should now be ready for use with IPA. 3. Now try login to workstation.mydomain.com using GDM using the smartcard issued for user3 Note! user3 password must not have been expired, it should be fixed by the initial login test above. As per details above: 1. Fedora 32 Workstation GDM menu prompts a few users that can login. 2. Smartcard is inserted in reader. 3. GDM blanks out the screen and smartcard reader prompts to enter PIN in its lcd display. 4. Entering pin on smartcard reader followed by pressing ok button on smartcard reader at getting result Pin OK in reader display. 5. GDM now prompts for entering PIN on keyboard, this is unexpected, instead of directly being logged in to the window manager, here Gnome (or xfce, whatever window manager you selected to use). 6. You have to enter the PIN now on keyboard, followed by hitting enter. 7. Once again smartcard reader now prompts for PIN in its lcd display. 8. Entering PIN on the smartcard pinpad reader followed by pressing pinpad ok button. 9. You are now logged in, and all is normal. If ripping out the smartcard from reader the screen locks, as expected. Sometimes, but not always, you are logged in to window manager directly after step 5. Actual Results: You are asked to enter PIN using pinpad on card reader followed by enter PIN using the keyboard, then you are logged in. Sometimes you need to enter PIN on pinpad once more after entering PIN using the keyboard. Expected Results: Directly after entering correct PIN using pinpad on card reader you should be logged in. Versions: Fedora32 with latest updates per Oct 9 2020. freeipa-server-4.8.10-5.fc32.x86_64 freeipa-client-4.8.10-5.fc32.x86_64 sssd-client-2.3.1-2.fc32.x86_64 opensc-0.20.0-6.fc32.x86_64 pcsc-lite-libs-1.9.0-1.fc32.x86_64 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 13

[Bug 2264610] New: FTBFS: sssd intermediate CA tests fail with OpenSSL 3.2
by bugzilla＠redhat.com 18 Oct '24

18 Oct '24

https://bugzilla.redhat.com/show_bug.cgi?id=2264610 Bug ID: 2264610 Summary: FTBFS: sssd intermediate CA tests fail with OpenSSL 3.2 Product: Fedora Version: rawhide OS: Linux Status: NEW Component: sssd Severity: medium Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: sgallagh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, lslebodn(a)redhat.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora $ /usr/bin/make -C src/tests/test_CA/intermediate_CA ca_all make: Entering directory '/home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA' test -z "index.txt index.txt.attr index.txt.attr.old index.txt.old SSSD_test_intermediate_CA.pem SSSD_test_intermediate_CA_req.pem SSSD_test_intermediate_CA_full_db.pem SSSD_test_CA.pem pwdfile SSSD_test_intermediate_CA_cert_x509_0001.pem SSSD_test_intermediate_CA_cert_x509_0001.h SSSD_test_intermediate_CA_cert_pubsshkey_0001.pub SSSD_test_intermediate_CA_cert_pubsshkey_0001.h SSSD_test_intermediate_CA_cert_pkcs12_0001.pem softhsm2_*.conf " || rm -f index.txt index.txt.attr index.txt.attr.old index.txt.old SSSD_test_intermediate_CA.pem SSSD_test_intermediate_CA_req.pem SSSD_test_intermediate_CA_full_db.pem SSSD_test_CA.pem pwdfile SSSD_test_intermediate_CA_cert_x509_0001.pem SSSD_test_intermediate_CA_cert_x509_0001.h SSSD_test_intermediate_CA_cert_pubsshkey_0001.pub SSSD_test_intermediate_CA_cert_pubsshkey_0001.h SSSD_test_intermediate_CA_cert_pkcs12_0001.pem softhsm2_*.conf rm -rf .libs _libs rm -rf newcerts rm -rf softhsm* rm -rf serial* rm -f *.lo /usr/bin/make -C ./.. SSSD_test_CA.pem make[1]: Entering directory '/home/sgallagh/localworkspace/sssd/src/tests/test_CA' /usr/bin/openssl req -batch -config ./SSSD_test_CA.config -x509 -new -nodes -key SSSD_test_CA_key.pem -sha256 -days 1024 -set_serial 0 -extensions v3_ca -out SSSD_test_CA.pem make[1]: Leaving directory '/home/sgallagh/localworkspace/sssd/src/tests/test_CA' ln -s ./../SSSD_test_CA.pem /usr/bin/openssl req -batch -config ./SSSD_test_intermediate_CA.config -new -nodes -key /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/SSSD_test_intermediate_CA_key.pem -sha256 -out SSSD_test_intermediate_CA_req.pem cd .. && /usr/bin/openssl ca -config /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/../SSSD_test_CA.config -batch -notext -keyfile /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/../SSSD_test_CA_key.pem -in /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/SSSD_test_intermediate_CA_req.pem -days 200 -extensions v3_intermediate_ca -out /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/SSSD_test_intermediate_CA.pem Using configuration from /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/../SSSD_test_CA.config Check that the request matches the signature Signature ok ERROR:There is already a certificate for /O=SSSD/OU=SSSD test/CN=SSSD test intermediate CA The matching entry has the following details Type :Valid Expires on :240903175906Z Serial Number :08 File name :unknown Subject Name :/O=SSSD/OU=SSSD test/CN=SSSD test intermediate CA make: *** [Makefile:756: SSSD_test_intermediate_CA.pem] Error 1 make: Leaving directory '/home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA' Reproducible: Always Steps to Reproduce: 1.Build SSSD and run the intermediate CA tests 2. 3. Actual Results: $ /usr/bin/make -C src/tests/test_CA/intermediate_CA ca_all make: Entering directory '/home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA' test -z "index.txt index.txt.attr index.txt.attr.old index.txt.old SSSD_test_intermediate_CA.pem SSSD_test_intermediate_CA_req.pem SSSD_test_intermediate_CA_full_db.pem SSSD_test_CA.pem pwdfile SSSD_test_intermediate_CA_cert_x509_0001.pem SSSD_test_intermediate_CA_cert_x509_0001.h SSSD_test_intermediate_CA_cert_pubsshkey_0001.pub SSSD_test_intermediate_CA_cert_pubsshkey_0001.h SSSD_test_intermediate_CA_cert_pkcs12_0001.pem softhsm2_*.conf " || rm -f index.txt index.txt.attr index.txt.attr.old index.txt.old SSSD_test_intermediate_CA.pem SSSD_test_intermediate_CA_req.pem SSSD_test_intermediate_CA_full_db.pem SSSD_test_CA.pem pwdfile SSSD_test_intermediate_CA_cert_x509_0001.pem SSSD_test_intermediate_CA_cert_x509_0001.h SSSD_test_intermediate_CA_cert_pubsshkey_0001.pub SSSD_test_intermediate_CA_cert_pubsshkey_0001.h SSSD_test_intermediate_CA_cert_pkcs12_0001.pem softhsm2_*.conf rm -rf .libs _libs rm -rf newcerts rm -rf softhsm* rm -rf serial* rm -f *.lo /usr/bin/make -C ./.. SSSD_test_CA.pem make[1]: Entering directory '/home/sgallagh/localworkspace/sssd/src/tests/test_CA' /usr/bin/openssl req -batch -config ./SSSD_test_CA.config -x509 -new -nodes -key SSSD_test_CA_key.pem -sha256 -days 1024 -set_serial 0 -extensions v3_ca -out SSSD_test_CA.pem make[1]: Leaving directory '/home/sgallagh/localworkspace/sssd/src/tests/test_CA' ln -s ./../SSSD_test_CA.pem /usr/bin/openssl req -batch -config ./SSSD_test_intermediate_CA.config -new -nodes -key /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/SSSD_test_intermediate_CA_key.pem -sha256 -out SSSD_test_intermediate_CA_req.pem cd .. && /usr/bin/openssl ca -config /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/../SSSD_test_CA.config -batch -notext -keyfile /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/../SSSD_test_CA_key.pem -in /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/SSSD_test_intermediate_CA_req.pem -days 200 -extensions v3_intermediate_ca -out /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/SSSD_test_intermediate_CA.pem Using configuration from /home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA/../SSSD_test_CA.config Check that the request matches the signature Signature ok ERROR:There is already a certificate for /O=SSSD/OU=SSSD test/CN=SSSD test intermediate CA The matching entry has the following details Type :Valid Expires on :240903175906Z Serial Number :08 File name :unknown Subject Name :/O=SSSD/OU=SSSD test/CN=SSSD test intermediate CA make: *** [Makefile:756: SSSD_test_intermediate_CA.pem] Error 1 make: Leaving directory '/home/sgallagh/localworkspace/sssd/src/tests/test_CA/intermediate_CA' Expected Results: Successful test run. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2264610 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 8

[Bug 2247777] New: SSSD will not boot up after restart
by bugzilla＠redhat.com 31 May '24

31 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2247777 Bug ID: 2247777 Summary: SSSD will not boot up after restart Product: Fedora Version: 38 Hardware: x86_64 URL: https://github.com/Scribery/cockpit-session-recording/ issues/157 OS: Linux Status: NEW Component: sssd Severity: medium Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: lzap(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, lslebodn(a)redhat.com, luk.claes(a)gmail.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora I installed a fresh Fedora 38, installed Session Recording in Cockpit, enabled All recording and SSSD does not start anymore. The error is: Condition ConditionPathExists=/etc/sssd/sssd.conf was not met. I think previously it was booting up properly. I reported to Cockpit guys via Slack, I was told to create a bug for the Session Recording plugin so I did: https://github.com/Scribery/cockpit-session-recording/issues/157 It looks like this might be a bug in the systemd unit file: "The SSSD unit file should also have ConditionDirectoryNotEmpty=|/etc/sssd/conf.d/" So leaving a bugreport for you guys. Reproducible: Always Steps to Reproduce: 1. Enable Session Recording via plugin as described 2. Sssd will not start anymore 3. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2247777 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 9

[Bug 2244284] New: [abrt] sssd-common: sasl_gss_encode(): sssd_be killed by SIGSEGV
by bugzilla＠redhat.com 31 May '24

31 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2244284 Bug ID: 2244284 Summary: [abrt] sssd-common: sasl_gss_encode(): sssd_be killed by SIGSEGV Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:167ab957ac30bea411e21fbfdfd50afe732488b8;VAR IANT_ID=; Component: sssd Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: brian(a)interlinx.bc.ca QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, lslebodn(a)redhat.com, luk.claes(a)gmail.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: Don't know why this happened. Version-Release number of selected component: sssd-common-2.9.1-1.fc38 Additional info: reporter: libreport-2.17.11 rootdir: / executable: /usr/libexec/sssd/sssd_be cmdline: /usr/libexec/sssd/sssd_be --domain interlinx.bc.ca --uid 0 --gid 0 --logger=files cgroup: 0::/system.slice/sssd.service journald_cursor: s=95d88e9521104634b5954ce8c2ca364c;i=1f78a94;b=04369d90e8d5440f8d4e37b41ad3728d;m=43205770ddc;t=607af55d9be18;x=1f1c6f3eef831d7f package: sssd-common-2.9.1-1.fc38 uid: 0 runlevel: N 5 crash_function: sasl_gss_encode comment: Don't know why this happened. backtrace_rating: 4 type: CCpp kernel: 6.4.11-200.fc38.x86_64 reason: sssd_be killed by SIGSEGV Truncated backtrace: Thread no. 1 (37 frames) #0 sasl_gss_encode at /usr/src/debug/cyrus-sasl-2.1.28-9.fc38.x86_64/plugins/gssapi.c:370 #1 _sasl_encodev at /usr/src/debug/cyrus-sasl-2.1.28-9.fc38.x86_64/lib/common.c:359 #2 sasl_encodev at /usr/src/debug/cyrus-sasl-2.1.28-9.fc38.x86_64/lib/common.c:582 #3 sasl_encode at /usr/src/debug/cyrus-sasl-2.1.28-9.fc38.x86_64/lib/common.c:304 #4 sb_sasl_cyrus_encode at /usr/src/debug/openldap-2.6.4-1.fc38.x86_64/openldap-2.6.4/libraries/libldap/cyrus.c:157 #5 sb_sasl_generic_write at /usr/src/debug/openldap-2.6.4-1.fc38.x86_64/openldap-2.6.4/libraries/libldap/sasl.c:783 #6 sb_debug_write at /usr/src/debug/openldap-2.6.6-1.fc38.x86_64/openldap-2.6.6/libraries/liblber/sockbuf.c:854 #8 ber_int_sb_write at /usr/src/debug/openldap-2.6.6-1.fc38.x86_64/openldap-2.6.6/libraries/liblber/sockbuf.c:445 #9 ber_flush2 at /usr/src/debug/openldap-2.6.6-1.fc38.x86_64/openldap-2.6.6/libraries/liblber/io.c:249 #10 ldap_int_flush_request at /usr/src/debug/openldap-2.6.4-1.fc38.x86_64/openldap-2.6.4/libraries/libldap/request.c:186 #11 ldap_send_server_request at /usr/src/debug/openldap-2.6.4-1.fc38.x86_64/openldap-2.6.4/libraries/libldap/request.c:412 #12 ldap_send_initial_request at /usr/src/debug/openldap-2.6.4-1.fc38.x86_64/openldap-2.6.4/libraries/libldap/request.c:169 #13 ldap_pvt_search at /usr/src/debug/openldap-2.6.4-1.fc38.x86_64/openldap-2.6.4/libraries/libldap/search.c:128 #14 ldap_search_ext at /usr/src/debug/openldap-2.6.4-1.fc38.x86_64/openldap-2.6.4/libraries/libldap/search.c:69 #15 sdap_get_generic_ext_step at src/providers/ldap/sdap_async.c:1664 #16 sdap_get_generic_ext_send at src/providers/ldap/sdap_async.c:1602 #17 sdap_get_and_parse_generic_send at src/providers/ldap/sdap_async.c:2055 #18 sdap_get_generic_send at src/providers/ldap/sdap_async.c:2156 #19 ipa_get_config_send at src/providers/ipa/ipa_config.c:93 #20 ipa_subdomains_passkey_send at src/providers/ipa/ipa_subdomains_passkey.c:64 #21 ipa_subdomains_refresh_certmap_done at src/providers/ipa/ipa_subdomains.c:2765 #22 _tevent_req_error at ../../tevent_req.c:221 #23 ipa_subdomains_certmap_done at src/providers/ipa/ipa_subdomains.c:1168 #24 _tevent_req_error at ../../tevent_req.c:221 #26 generic_ext_search_handler.isra.0 at src/providers/ldap/sdap_async.c:1983 #27 _tevent_req_error at ../../tevent_req.c:221 #28 sdap_get_generic_op_finished at src/providers/ldap/sdap_async.c:1774 #29 sdap_handle_release at src/providers/ldap/sdap_async.c:143 #30 sdap_process_result at src/providers/ldap/sdap_async.c:245 #31 tevent_common_invoke_fd_handler at ../../tevent_fd.c:142 #32 epoll_event_loop at ../../tevent_epoll.c:737 #33 epoll_event_loop_once at ../../tevent_epoll.c:938 #34 std_event_loop_once at ../../tevent_standard.c:110 #35 _tevent_loop_once at ../../tevent.c:823 #36 tevent_common_loop_wait at ../../tevent.c:949 #37 std_event_loop_wait at ../../tevent_standard.c:141 #38 server_loop at src/util/server.c:787 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2244284 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 1

[Bug 2214534] New: [abrt] sssd-common: __strcmp_avx2(): sssd_be killed by SIGSEGV
by bugzilla＠redhat.com 22 May '24

22 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2214534 Bug ID: 2214534 Summary: [abrt] sssd-common: __strcmp_avx2(): sssd_be killed by SIGSEGV Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:a07038fd78acc47fd66b266203cafebd50509e00;VAR IANT_ID=workstation; Component: sssd Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: jortialc(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, jhrozek(a)redhat.com, lslebodn(a)redhat.com, luk.claes(a)gmail.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: This happens when doing some privilege escalation like using sudo or the authentication required dialog in Gnome Version-Release number of selected component: sssd-common-2.9.0-1.fc38 Additional info: reporter: libreport-2.17.10 type: CCpp reason: sssd_be killed by SIGSEGV journald_cursor: s=025af2782fd445c2a5eb791571c74138;i=250aa;b=61468fbb4dd141e9b488d260f287c4ef;m=69ee27e2a;t=5fd9e17d98e50;x=b86133abd50e6842 executable: /usr/libexec/sssd/sssd_be cmdline: /usr/libexec/sssd/sssd_be --domain ipa.redhat.com --uid 0 --gid 0 --logger=files cgroup: 0::/system.slice/sssd.service rootdir: / uid: 0 kernel: 6.3.5-200.fc38.x86_64 package: sssd-common-2.9.0-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: __strcmp_avx2 comment: This happens when doing some privilege escalation like using sudo or the authentication required dialog in Gnome Truncated backtrace: Thread no. 1 (21 frames) #0 __strcmp_avx2 at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283 #1 be_resolve_server_process at src/providers/data_provider_fo.c:691 #2 be_resolve_server_done at src/providers/data_provider_fo.c:557 #3 fo_resolve_service_server at src/providers/fail_over.c:1169 #4 _tevent_req_error at ../../tevent_req.c:221 #5 resolve_srv_done at src/providers/fail_over.c:1480 #6 fo_discover_srv_done at src/providers/fail_over_srv.c:141 #7 resolv_getsrv_done at src/resolv/async_resolv.c:1877 #8 qcallback at /usr/src/debug/c-ares-1.19.1-1.fc38.x86_64/src/lib/ares_query.c:143 #9 end_query at /usr/src/debug/c-ares-1.19.1-1.fc38.x86_64/src/lib/ares_process.c:1525 #10 process_answer at /usr/src/debug/c-ares-1.19.1-1.fc38.x86_64/src/lib/ares_process.c:598 #11 read_udp_packets at /usr/src/debug/c-ares-1.19.1-1.fc38.x86_64/src/lib/ares_process.c:548 #12 processfds at /usr/src/debug/c-ares-1.19.1-1.fc38.x86_64/src/lib/ares_process.c:126 #13 tevent_common_invoke_fd_handler at ../../tevent_fd.c:142 #14 epoll_event_loop at ../../tevent_epoll.c:737 #15 epoll_event_loop_once at ../../tevent_epoll.c:938 #16 std_event_loop_once at ../../tevent_standard.c:110 #17 _tevent_loop_once at ../../tevent.c:823 #18 tevent_common_loop_wait at ../../tevent.c:949 #19 std_event_loop_wait at ../../tevent_standard.c:141 #20 server_loop at src/util/server.c:787 Potential duplicate: bug 1773488 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2214534 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 15

[Bug 2275905] New: TRIAGE CVE-2023-3758 sssd: Race condition during authorization leads to GPO policies functioning inconsistently [fedora-all]
by bugzilla＠redhat.com 08 May '24

08 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2275905 Bug ID: 2275905 Summary: TRIAGE CVE-2023-3758 sssd: Race condition during authorization leads to GPO policies functioning inconsistently [fedora-all] Product: Fedora Version: 39 Status: NEW Component: sssd Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: askrabec(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, lslebodn(a)redhat.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2223762 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275905 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 14

[Bug 2272913] New: sssd: FTBFS in Fedora Rawhide
by bugzilla＠redhat.com 03 Apr '24

03 Apr '24

https://bugzilla.redhat.com/show_bug.cgi?id=2272913 Bug ID: 2272913 Summary: sssd: FTBFS in Fedora Rawhide Product: Fedora Version: rawhide URL: https://koschei.fedoraproject.org/package/sssd OS: Linux Status: NEW Component: sssd Severity: medium Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: ksurma(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, lslebodn(a)redhat.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: Package sssd fails to build from source in Fedora Rawhide. Version-Release number of selected component (if applicable): 2.9.4-4.fc40 Steps to Reproduce: koji build --scratch f41 sssd-2.9.4-4.fc40.src.rpm Additional info: This package is tracked by Koschei. See: https://koschei.fedoraproject.org/package/sssd Reproducible: Always Actual Results: make[1]: Entering directory '/builddir/build/BUILD/sssd-2.9.4/src/tests/test_CA/intermediate_CA' /usr/bin/openssl req -batch -config ./SSSD_test_intermediate_CA.config -new -nodes -key /builddir/build/BUILD/sssd-2.9.4/src/tests/test_CA/intermediate_CA/SSSD_test_intermediate_CA_key.pem -sha256 -extensions v3_ca -out SSSD_test_intermediate_CA_req.pem Error adding request extensions from section v3_ca 80F26618767F0000:error:11000079:X509 V3 routines:v2i_AUTHORITY_KEYID:no issuer certificate:crypto/x509/v3_akid.c:156: 80F26618767F0000:error:11000080:X509 V3 routines:X509V3_EXT_nconf_int:error in extension:crypto/x509/v3_conf.c:48:section=v3_ca, name=authorityKeyIdentifier, value=keyid:always,issuer:always make[1]: *** [Makefile:759: SSSD_test_intermediate_CA_req.pem] Error 1 make[1]: Leaving directory '/builddir/build/BUILD/sssd-2.9.4/src/tests/test_CA/intermediate_CA' make: *** [Makefile:47806: test_CA.stamp] Error 2 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2272913 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

2025

2024

2023

2022

2021

2020

Sssd-maintainers April 2024