On Wed, Oct 24, 2001 at 01:32:30AM +0000, Matthew Ceroni wrote:

> I ran the ldd command a turned out that I had was using PAM.
> 
> So I created the file ssh under the /etc/pam.d directory and copied the 
> example you gave me. However I still can't login..

(Example from Debian potato...)

> >   svr1a:/etc/pam.d# cat ssh
> >   #%PAM-1.0
> >   auth       required     pam_nologin.so
> >   auth       required     pam_unix.so
> >   auth       required     pam_env.so # [1]
> >
> >   account    required     pam_unix.so
> >
> >   session    required     pam_unix.so
> >   session    optional     pam_lastlog.so # [1]
> >   session    optional     pam_motd.so # [1]
> >   session    optional     pam_mail.so standard # [1]
> >
> >   password   required     pam_unix.so
> >
> >   # Alternate strength checking for password. Note that this
> >   # requires the libpam-cracklib package to be installed.
> >   # You will need to comment out the password line above and
> >   # uncomment the next two in order to use this.
> >   #
> >   # password required       pam_cracklib.so retry=3 minlen=6 difok=3
> >   # password required       pam_unix.so use_authtok nullok md5

I'm copying this back to the list, because other people may have
additional knowledge that could be helpful.

The most likely cause of problems is the use of MD5 passwords.  If
you're using MD5, then you need to indicate that in the pam.d/ssh
file.  Examine your /etc/pam.d/login file -- in particular, any lines
that use the "pam_unix.so" module.  If you have "md5" on that line,
then you will also need it on the corresponding pam_unix.so line in
the pam.d/ssh file.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to