You are not logged in.
Dear loqs & seth,
thank you very much for your help and patience. The problem was not with the /etc/pam.d/* files and eCryptfs but rather with the /etc/shells.pacnew provided by the new filesystem package. I merged them and overlooked the zsh entries which are not included in the new file. Since I use zsh as a shell, this led to disaster.
Thanks again & I owe you a beer. I'll set the post to solved.
Cheers hcjl
Offline
Misery loves company: https://bbs.archlinux.org/viewtopic.php … 1#p2117141
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
@schard: But at least you have not wasted the time of others ;-)
Offline
@schard: But at least you have not wasted the time of others ;-)
Well you certainly didn't waste mine since I had just the same issue with a comparable setup (fscrypt instead of ecryptfs) and started by downgrading pam and shadow before luckily stumbling on your thread and realized I too merged by mistake /etc/shells without including zsh as allowed login shells.
If anything you've just saved me hours of troubleshooting and made my day
Cheers mate!
Offline
I was about to say that maybe three years from now some random dude…
We also all learned that pam_shells fails pam completely silently on invalid shells (which seems a bug? it tells you when something's off w/ the etc/shells file, just not that your shell isn't in there and I don't see what sensitive data would get exposed by that) and can set a mental note for "inexplicable PAM failures"
And we learned that the smart way to merge /etc/shells is always "mine".
And we've learned that working around decade old bugs is maybe a bad idea.
All in all, there was much to learn from this thread
Online