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

swaylock: PAM doesn't use config file in /usr/local/etc/pam.d. #3096

Closed
c-edw opened this Issue Nov 10, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@c-edw
Copy link
Contributor

c-edw commented Nov 10, 2018

This is not an issue with sway or swaylock itself, but may be an installation issue on some systems. I have PAM installed on my Fedora 28 system, but it doesn't use the configuration file installed to /usr/local/etc/pam.d. When I use swaylock, it will lock me out because PAM isn't aware of this file. Moving it to /etc/pam.d fixes this.

I didn't notice this until now because I just removed the Sway (0.15) package, which places the configuration file at /etc/pam.d.

I assume that anybody building master is supposed to make a symlink or a copy to /etc/pam.d, but this should be noted somewhere.

@emersion

This comment has been minimized.

Copy link
Member

emersion commented Nov 17, 2018

Please send a PR.

@progandy

This comment has been minimized.

Copy link
Contributor

progandy commented Nov 23, 2018

Can you try to build with #3178 while setting sysconfdir to /etc? Of course, you'll have to make sure that the files in /etc aren't conflicting with packages you installed with you package manager, but everything except the pam configuration is in the /etc/sway/ directory

meson build -Dsysconfdir=/etc 
ninja -C build
sudo ninja -C build install
@c-edw

This comment has been minimized.

Copy link
Contributor Author

c-edw commented Nov 24, 2018

It works well. I am concerned though that needing to specify -Dsysconfdir will complicate the process for developers. Shouldn't this be the default, and if not, why?

@c-edw

This comment has been minimized.

Copy link
Contributor Author

c-edw commented Nov 27, 2018

Closing since the issue has been resolved, though I would like to continue this discussion.

@c-edw c-edw closed this Nov 27, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.