Package: libpam-ssh Version: 1.92-5 Severity: normal After upgrading from libpam-ssh 1.91.0-9.3 to libpam-ssh 1.92-5, libpam-ssh no longer uses my password to add my SSH keys to the ssh-agent it starts.
The changelog for libpam-ssh suggested that it would now unlock any key matching id_*, which my keys do. Another entry in the changelog suggested that libpam-ssh now looks for keys in $HOME/.ssh/login-keys.d/ , but I certainly hope it doesn't *require* keys to appear in that directory. That would represent a regression from previous versions, which found my keys without that extra configuration. - Josh Triplett -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-ssh depends on: ii libc6 2.9-4 GNU C Library: Shared libraries ii libpam0g 1.0.1-7 Pluggable Authentication Modules l ii libssl0.9.8 0.9.8g-15 SSL shared libraries Versions of packages libpam-ssh recommends: ii openssh-client [ssh-client] 1:5.1p1-5 secure shell client, an rlogin/rsh libpam-ssh suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
