openssh + pam authentication failing +md5 (?!) HELP HELP HELP !

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



--Uwl7UQhJk99r8jnw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, May 03, 2002 at 02:12:51AM -0700, light storm wrote:
> This is the first time i really needed to seek the help of some one
> who has alot more expertise on this subject since i have almost no
> hair left on my head which i didn't pull out ;-)=20

> I have installed: openssh 3.1 , openssl 0.9.6a and i use PAM , most
> things work perfect, till i wanted to use pam for ssh, i enable also
> pam support for openssh, also enable md5 passwords support for openssh
> , added the correct information to the pam file (/etc/pam.d/sshd) like
> 'md5' , but when i try to login from various servers to that server
> then shortly said i get "PAM authentication failed, permission denied
> ... " . that is the problem hehe

> Paste:

> Failed password for testuser from 192.168.150.52 port 34440 ssh2=20
> debug1: userauth-request for user testuser service ssh-connection method=
=20
> password=20
> debug1: attempt 3 failures 3=20
> debug2: input_userauth_request: try method password=20
> debug1: PAM Password authentication for "testuser" failed[7]:=20
> Authentication failure=20
> ...    =20

> my sshd_config, ssh_config are all correctly configured, beside the
> above passwd/login are also using PAM, no problem

> i did a test, i created with another tool a password for testuser, not
> md5, all of a sudden ssh worked (!??) , but when i change the pass
> with passwd (it then gets to be a md5) ssh refuses :((( ..

> IMHO something goes wrong when the md5 password is read by PAM and
> that causes openssh to say permission denied ... but guys, what in
> godsname goes wrong or what did i do wrong ?=20


> PS: the generic pam sshd file is what i use, added the md5 to it.

Please post the full contents of the exact PAM configuration you're
using for sshd.  There are many different 'default' configurations in
existence, and it's impossible to diagnose this error without knowing
what your particular configuration looks like.

Steve Langasek
postmodern programmer

--Uwl7UQhJk99r8jnw
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE80rqtKN6ufymYLloRAo+ZAJ4508T5jj7vTWmLfkpd6Lw+CQQ/IACfZWea
522dURA5d4g8Gk6pKaCRJP4=
=cNlF
-----END PGP SIGNATURE-----

--Uwl7UQhJk99r8jnw--





[Index of Archives]     [Fedora Users]     [Kernel]     [Red Hat Install]     [Linux for the blind]     [Gimp]

  Powered by Linux