-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
pam auth fails after upgrading from 16.06 to 16.08 #1281
Milestone
Comments
weiss
added a commit
to weiss/ejabberd
that referenced
this issue
Sep 16, 2016
The "NoNewPrivileges" setting breaks some PAM and extauth setups. Fixes processone#1281.
weiss
added a commit
to weiss/ejabberd
that referenced
this issue
Sep 16, 2016
The "NoNewPrivileges" setting breaks some PAM and extauth setups. Fixes processone#1281.
weiss
added a commit
to weiss/ejabberd
that referenced
this issue
Oct 19, 2016
The "NoNewPrivileges" setting breaks some PAM and extauth setups. Fixes processone#1281.
Holger's changes are merged, this can be closed now. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
16.08
Debian jessie 8.5
jessie-backports package version 16.08-1~bpo8+1
pam authentication does not work, the epam process is running as ejabberd:ejabberd even tho the binary is setgid shadow. Without group shadow pam cannot access /etc/shadow and so it can't authenticate the user.
I've had a dig around in the ejabberd and epam source code and can't see anything obvious unfortunately.
Note that the epam binary was not changed by the upgrade (or downgrade to 16.06)
Debian bug report is here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836711
The text was updated successfully, but these errors were encountered: