On 8 March 2010 14:38, Erich Schubert <er...@debian.org> wrote:
>
> * 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 suspect you are right.
> 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?
I do not see how.
Anyways, I will upload a new version of pamssh with proper prefixed
names to avoid conflicts.
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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
