Hi Dan,

> > This is the same problem than the one discussed in the following
> > thread:
> >

>

http://groups.google.de/group/linux....&start=0&num=3

> Do you engage PAM in authentication? Some poorly written PAM modules can
> block for some reason SIGALARM while not clearing that blocking before

starting
> user session. If sshd itself never blocks SIGALARM, one or more of PAM

modules
> could be the reason of that.


Yeah, that could be the problem indeed (the thread above mention a possible
PAM issue as well). Do you have an idea how I should proceed in order to
find out the broken PAM module(s)?

TIA,
Loic.

--
GMX DSL-Flatrate 1 Jahr kostenlos* + WLAN-Router ab 0,- Euro*
Bis 31.12.2005 einsteigen! Infos unter: http://www.gmx.net/de/go/dsl

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@mindrot.org
http://www.mindrot.org/mailman/listi...enssh-unix-dev