I am truly sorry that you are being bothered by the changes in the new Debian version of libpam-ssh.
The story is that the new version of libpam-ssh will look for keys in $HOME/.ssh/login-keys.d/, and only there. I implemented that functionality after a discussion on the debian-devel mailing list [1] and an announcement on pam mailing list (with no response). Since then, the new version of libpam-ssh has been available in experimental, and because I have had no complaints about it so far, I have uploaded it to unstable. Personally I think the new setup is better because it relieves the administrator from doing any special setup for users, while at the same time enabling individual users to use as many keys as they like (cf [3]). But maybe libpam-ssh should look for the same set as key as ssh does in addition to $HOME/.ssh/login-keys.d/ ? [1] http://lists.debian.org/debian-devel/2008/12/msg00193.html [2] https://www.redhat.com/archives/pam-list/2008-December/msg00004.html [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477272 Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
