Hello list, i know there are many threads about the actual OpenSSH and the upcoming problems. But i think my problem has not been discussed here before. After updating a SuSE 7.3 to OpenSSH 3.3.p1 no ssh login is possible. not as root and not as normal user. the password is always rejected. i think that it may be a problem with pam, but i'm not experienced enough to be sure. after some time of trying i deinstalled 3.3 and reinstalled 2.9p2 from suse 7.3 CDs. now login works again. theese are some messages that i got while debugging and they may be interesting: pleasure:/ # ./sshd -d debug1: sshd version OpenSSH_3.3 debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #1 type 2 DSA debug1: Bind to port 80 on ::. Server listening on :: port 80. --- no i try to connect --- debug1: Server will not fork when running in debugging mode. Connection from ::ffff:217.82.228.190 port 33275 debug1: Client protocol version 2.0; client software version OpenSSH_3.3 debug1: match: OpenSSH_3.3 pat OpenSSH* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.3 debug1: list_hostkey_types: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: client->server aes128-cbc hmac-md5 none debug1: kex: server->client aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent debug1: dh_gen_key: priv key bits set: 134/256 debug1: bits set: 1604/3191 debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT debug1: bits set: 1608/3191 debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: KEX done debug1: userauth-request for user root service ssh-connection method none debug1: attempt 0 failures 0 debug1: Starting up PAM with username "root" debug1: PAM setting rhost to "pd952e4be.dip.t-dialin.net" Failed none for root from ::ffff:217.82.228.190 port 33275 ssh2 Failed none for root from ::ffff:217.82.228.190 port 33275 ssh2 debug1: userauth-request for user root service ssh-connection method keyboard-interactive debug1: attempt 1 failures 1 debug1: keyboard-interactive devs debug1: auth2_challenge: user=root devs= debug1: kbdint_alloc: devices '' Failed keyboard-interactive for root from ::ffff:217.82.228.190 port 33275 ssh2 debug1: userauth-request for user root service ssh-connection method password debug1: attempt 2 failures 2 debug1: PAM Password authentication for "root" failed[7]: Authentication failure Failed password for root from ::ffff:217.82.228.190 port 33275 ssh2 Failed password for root from ::ffff:217.82.228.190 port 33275 ssh2 debug1: userauth-request for user root service ssh-connection method password debug1: attempt 3 failures 3 Failed password for root from ::ffff:217.82.228.190 port 33275 ssh2 Failed password for root from ::ffff:217.82.228.190 port 33275 ssh2 debug1: userauth-request for user root service ssh-connection method password debug1: attempt 4 failures 4 Failed password for root from ::ffff:217.82.228.190 port 33275 ssh2 Failed password for root from ::ffff:217.82.228.190 port 33275 ssh2 Connection closed by ::ffff:217.82.228.190 debug1: Calling cleanup 0x806ec80(0x0) debug1: Calling cleanup 0x8053dc0(0x0) debug1: Calling cleanup 0x806ec80(0x0) This is my pam config (it's the suse default) #%PAM-1.0 auth required pam_unix.so # set_secrpc auth required pam_nologin.so auth required pam_env.so account required pam_unix.so password required pam_pwcheck.so password required pam_unix.so use_first_pass use_authtok session required pam_unix.so none # trace or debug session required pam_limits.so Does anyone see whats wrong? Any ideas how to solve this or what to try? Thank you very much! Thomas