Skip to content
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

Handle PAM session and account stack #29

Open
rhopfer opened this issue Jul 30, 2015 · 1 comment
Open

Handle PAM session and account stack #29

rhopfer opened this issue Jul 30, 2015 · 1 comment

Comments

@rhopfer
Copy link

rhopfer commented Jul 30, 2015

At the moment it seams i3lock only handle the auth stack.

If pam_krb5 is used for authentication, the auth stack stores the credentials in a temprary file (/tmp/krb5_pam_XXXXXX). During session stack (pam_sm_setcred), the credentials are moved to its final location (/tmp/krb5cc_UID_XXXXXX) and the environment variable KRB5CCNAME will be set.

@stapelberg
Copy link
Member

Can you send a pull request which makes the necessary changes please? I don’t have Kerberos set up in my environments anymore, so it would go a long way if you could send the PR :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants