-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cups pam auth via ldap segfault #5327
Comments
Does this happen with the default pam module or just pam_ldap? |
Looking fine with pam_unix |
I'm guessing that the pam_ldap module is doing something with GNU TLS that is interfering with cupsd's usage. What does ldd show for the pam_ldap.so file? |
Looks like neither can be compiled with openssl instead gnutls. |
It shouldn't be necessary, but if they use GNU TLS in an unsafe way bad things will happen... Right now the best thing is probably to file a bug on the Ubuntu tracker - I'm not sure which version of pam_ldap Ubuntu is using, or where the GNU TLS dependencies intersect (i.e. is it OpenLDAP or Heimdal or ???) I'll keep this bug open until a root cause is found, then we can determine how best to fix it... |
Well it is pam_ldap, I was able to fix the issue with a manually compiled version of https://github.com/arthurdejong/nss-pam-ldapd instead of libpam-ldap. ubuntu bug related to libpam-ldap: https://bugs.launchpad.net/ubuntu/+source/libpam-ldap/+bug/1776484 |
still trying to achieve ldap authentication.
I guess I do not really need to deploy the ldap users via nss to the system, pam auth via ldap should be enough right?
Because it kinda works, I can authenticate (web ui), and most time get the page back but cupsd will crash every time after ~3s.
cups version: built from latest stable release v2.2.8
cups log:
stacktrace:
Note:
With the builds from ubuntu v2.1.x I get a segfault in libnss_dns:
kernel: [2763212.200780] cupsd[31100]: segfault at 7fd886e983f0 ip 00007fd886e983f0 sp 00007fff8b2338c8 error 14 in libnss_dns-2.23.so[7fd8872bd000+5000
The text was updated successfully, but these errors were encountered: