Summary: | sys-auth/pam_ssh-2.1 won't accept my ssh passphrase | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | walt <wsheets> |
Component: | [OLD] Core system | Assignee: | PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
walt
2015-07-07 15:44:14 UTC
Same issue here on ~AMD64, though my system is shamefully unstable due to compile flags. Adding this as the OP's seems sane. Jul 9 10:18:58 peen pam_ssh[7582]: init authentication module Jul 9 10:18:58 peen pam_ssh[7582]: No SSH login-keys directory. Jul 9 10:18:58 peen pam_ssh[7582]: Asking for SSH key passphrase. Jul 9 10:19:03 peen pam_ssh[7582]: Looking for SSH keys in '/home/sietze/.ssh/session-keys.d'. Jul 9 10:19:03 peen pam_ssh[7582]: No SSH session-keys directory. Jul 9 10:19:03 peen pam_ssh[7582]: Looking for SSH keys in '/home/sietze/.ssh/login-keys.d'. Jul 9 10:19:03 peen pam_ssh[7582]: Looking for SSH keys in '/home/sietze/.ssh'. Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'id_ed25519'. Jul 9 10:19:03 peen pam_ssh[7582]: debug1: key_load_private: No such file or directory Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'id_ed25519' failed. Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'id_ecdsa'. Jul 9 10:19:03 peen pam_ssh[7582]: debug1: key_load_private: No such file or directory Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'id_ecdsa' failed. Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'id_dsa'. Jul 9 10:19:03 peen pam_ssh[7582]: debug1: key_load_private: No such file or directory Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'id_dsa' failed. Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'id_rsa'. Jul 9 10:19:03 peen pam_ssh[7582]: SSH key 'id_rsa' decrypted. Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'identity'. Jul 9 10:19:03 peen pam_ssh[7582]: debug1: key_load_private: No such file or directory Jul 9 10:19:03 peen pam_ssh[7582]: SSH key candidate 'identity' failed. Jul 9 10:19:03 peen login[7582]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=****** Jul 9 10:19:07 peen login[7582]: FAILED LOGIN (1) on '/dev/tty1' FOR '******', Authentication failure My private key file ~/.ssh/id_rsa seems found and decrypted. creating a directory # mkdir ~/.ssh/login-keys.d and linking my keys used for loggin in there # ln -sf ~/.ssh/id_rsa ~/.ssh/login-keys.d/ allows me to log in again with SSH keys. This seems to be mentioned in the ChangeLog, Version 2.0, 2013-11-10: Look for SSH keys in $HOME/.ssh/login-keys.d/, given that SSH keys with .disabled or .frozen as suffix are ignored. It could've been clearer, maybe even an einfo in the ebuild? Thank you. Adding the new directory and symlink fixed the problem. Questions: is this change coming from upstream or from gentoo? What problem is it solving? (In reply to walt from comment #3) Gentoo maintains no patches on pam_ssh. all behavior changes are from upstream. should be all set now in the tree; thanks for the report! Commit message: Add notice for upstream changes wrt ~/.ssh/login-keys.d/ http://sources.gentoo.org/sys-auth/pam_ssh/pam_ssh-2.1.ebuild?r1=1.1&r2=1.2 |