Hi Rhonsa, Timo, For me the bug just surfaced sometime in February 2010 on unstable. So I'd assume it only surfaced for me with the 1.92-10 release.
But I never _configured_ libpam-ssh, and given that the changelog reads: * Use pam-auth-update together with the new setup file /usr/share/pam-configs/silent-ssh-single-sign-on to automatically enable the traditional functionality. My best guess is just that this new configuration setup caused the module to become activated while it wasn't before. So the bug could have been present for much longer when libpam-ssh was actually configured. I wonder whether there is a way to check for such errors automatically with lintian; they are bound to arise now and then, aren't they? Regards, Erich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
