Re: sshd & pam & getpwnam()

2004-06-28 Thread Danny Braniss
> Sun, Jun 20, 2004 at 14:52:35, zagarin wrote about "sshd & pam & getpwnam()": > > > Does anybody know, why sshd call getpwnam() even if user is > > authenticating via PAM? This broke remote authentication (RADIUS, > > TACACS+) when user doesn't

Re: sshd & pam & getpwnam()

2004-06-28 Thread Valentin Nechayev
Sun, Jun 20, 2004 at 14:52:35, zagarin wrote about "sshd & pam & getpwnam()": > Does anybody know, why sshd call getpwnam() even if user is > authenticating via PAM? This broke remote authentication (RADIUS, > TACACS+) when user doesn't exist in local passwor

Re: sshd & pam & getpwnam()

2004-06-28 Thread Gordon Tetlow
On Sun, Jun 20, 2004 at 02:52:35PM +0400, Alexey Zagarin wrote: > Hello! > > Does anybody know, why sshd call getpwnam() even if user is > authenticating via PAM? This broke remote authentication (RADIUS, > TACACS+) when user doesn't exist in local password database. The user must exist in some

Re: sshd & pam & getpwnam()

2004-06-24 Thread Nick Rogness
On Sun, 20 Jun 2004, Alexey Zagarin wrote: Hello! Does anybody know, why sshd call getpwnam() even if user is authenticating via PAM? This broke remote authentication (RADIUS, TACACS+) when user doesn't exist in local password database. This is typical behavior for most account based PAM appl

sshd & pam & getpwnam()

2004-06-20 Thread Alexey Zagarin
Hello! Does anybody know, why sshd call getpwnam() even if user is authenticating via PAM? This broke remote authentication (RADIUS, TACACS+) when user doesn't exist in local password database. -- Alexey Zagarin emax telecommunications ___ [EMAIL PROTE