[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ssh + kerberosV
On Sat, 2003-11-29 at 17:14, Julien TOUCHE wrote:
> Matthijs Mohlmann wrote:
>
> > Your ssh daemon and client doesn't have kerberos support.
> >
> > I've both enabled GSSAPIAuthentication and KerberosAuthentication.
> >
> > your login.conf is ok but ssh doesn't use /bin/login so you need to
> > enable gssapi support in ssh
> >
> ok, done
>
> # more log2
> debug2: read_server_config: filename /etc/ssh/sshd_config
> debug1: sshd version OpenSSH_3.7.1
> debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key.
> debug1: read PEM private key done: type RSA
> debug1: private host key: #0 type 1 RSA
> debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key.
> debug1: read PEM private key done: type DSA
> debug1: private host key: #1 type 2 DSA
> debug1: Bind to port 22 on ::.
> Server listening on :: port 22.
> debug1: Bind to port 22 on 0.0.0.0.
> Server listening on 0.0.0.0 port 22.
> debug1: Server will not fork when running in debugging mode.
> Connection from 192.168.2.5 port 24831
> debug1: Client protocol version 2.0; client software version OpenSSH_3.7.1
> debug1: match: OpenSSH_3.7.1 pat OpenSSH*
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_3.7.1
> debug2: Network child is on pid 12480
> debug3: preauth child monitor started
> debug3: mm_request_receive entering
> debug3: privsep user:group 27:27
> debug1: permanently_set_uid: 27/27
> debug1: list_hostkey_types: ssh-rsa,ssh-dss
> debug1: SSH2_MSG_KEXINIT sent
> debug1: SSH2_MSG_KEXINIT received
> debug2: kex_parse_kexinit:
> diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
> debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
> debug2: kex_parse_kexinit:
> aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysat
> or.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
> debug2: kex_parse_kexinit:
> aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysat
> or.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
> debug2: kex_parse_kexinit:
> hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
> debug2: kex_parse_kexinit:
> hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
> debug2: kex_parse_kexinit: none,zlib
> debug2: kex_parse_kexinit: none,zlib
> debug2: kex_parse_kexinit:
> debug2: kex_parse_kexinit:
> debug2: kex_parse_kexinit: first_kex_follows 0
> debug2: kex_parse_kexinit: reserved 0
> debug2: kex_parse_kexinit:
> diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
> debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
> debug2: kex_parse_kexinit:
> aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysat
> or.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
> debug2: kex_parse_kexinit:
> aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysat
> or.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
> debug2: kex_parse_kexinit:
> hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
> debug2: kex_parse_kexinit:
> hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
> debug2: kex_parse_kexinit: none,zlib
> debug2: kex_parse_kexinit: none,zlib
> debug2: kex_parse_kexinit:
> debug2: kex_parse_kexinit:
> debug2: kex_parse_kexinit: first_kex_follows 0
> debug2: kex_parse_kexinit: reserved 0
> debug2: mac_init: found hmac-md5
> debug1: kex: client->server aes128-cbc hmac-md5 none
> debug2: mac_init: found hmac-md5
> debug1: kex: server->client aes128-cbc hmac-md5 none
> debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received
> debug3: mm_request_send entering: type 0
> debug3: monitor_read: checking request 0
> debug3: mm_answer_moduli: got parameters: 1024 2048 8192
> debug3: mm_choose_dh: waiting for MONITOR_ANS_MODULI
> debug3: mm_request_receive_expect entering: type 1
> debug3: mm_request_receive entering
> debug3: mm_request_send entering: type 1
> debug3: mm_choose_dh: remaining 0
> debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
> debug2: monitor_read: 0 used once, disabling now
> debug3: mm_request_receive entering
> debug2: dh_gen_key: priv key bits set: 120/256
> debug2: bits set: 1565/3191
> debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
> debug2: bits set: 1633/3191
> debug3: mm_key_sign entering
> debug3: mm_request_send entering: type 4
> debug3: monitor_read: checking request 4
> debug3: mm_answer_sign
> debug3: mm_answer_sign: signature 0x3c029200(143)
> debug3: mm_request_send entering: type 5
> debug2: monitor_read: 4 used once, disabling now
> debug3: mm_request_receive entering
> debug3: mm_key_sign: waiting for MONITOR_ANS_SIGN
> debug3: mm_request_receive_expect entering: type 5
> debug3: mm_request_receive entering
> debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
> debug2: kex_derive_keys
> debug2: set_newkeys: mode 1
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug2: set_newkeys: mode 0
> debug1: SSH2_MSG_NEWKEYS received
> debug1: KEX done
> debug1: userauth-request for user touche service ssh-connection method none
> debug1: attempt 0 failures 0
> debug3: mm_getpwnamallow entering
> debug3: mm_request_send entering: type 6
> debug3: monitor_read: checking request 6
> debug3: mm_answer_pwnamallow
> debug3: Trying to reverse map address 192.168.2.5.
> debug3: mm_answer_pwnamallow: sending MONITOR_ANS_PWNAM: 1
> debug3: mm_request_send entering: type 7
> debug2: monitor_read: 6 used once, disabling now
> debug3: mm_request_receive entering
> debug3: mm_getpwnamallow: waiting for MONITOR_ANS_PWNAM
> debug3: mm_request_receive_expect entering: type 7
> debug3: mm_request_receive entering
> debug2: input_userauth_request: setting up authctxt for touche
> debug3: mm_inform_authserv entering
> debug3: mm_request_send entering: type 3
> debug3: monitor_read: checking request 3
> debug3: mm_answer_authserv: service=ssh-connection, style=
> debug2: monitor_read: 3 used once, disabling now
> debug3: mm_request_receive entering
> debug2: input_userauth_request: try method none
> debug3: mm_auth_password entering
> debug3: mm_request_send entering: type 10
> debug3: monitor_read: checking request 10
> debug3: mm_answer_authpassword: sending result 0
> debug3: mm_request_send entering: type 11
> Failed none for touche from 192.168.2.5 port 24831 ssh2
> debug3: mm_request_receive entering
> debug3: mm_auth_password: waiting for MONITOR_ANS_AUTHPASSWORD
> debug3: mm_request_receive_expect entering: type 11
> debug3: mm_request_receive entering
> debug3: mm_auth_password: user not authenticated
> Failed none for touche from 192.168.2.5 port 24831 ssh2
> debug1: userauth-request for user touche service ssh-connection method
> gssapi
> debug1: attempt 1 failures 1
> debug2: input_userauth_request: try method gssapi
> debug3: mm_request_send entering: type 37
> debug3: monitor_read: checking request 37
> debug3: mm_request_send entering: type 38
> debug3: mm_request_receive entering
> debug3: mm_request_receive_expect entering: type 38
> debug3: mm_request_receive entering
> Postponed gssapi for touche from 192.168.2.5 port 24831 ssh2
> debug3: mm_request_send entering: type 39
> debug3: monitor_read: checking request 39
> debug1: Miscellaneous failure (see text)
> Decrypt integrity check failed
>
> debug1: Got no client credentials
Got no client credentials ...
Do you have in /etc/ssh/ssh_config:
KerberosAuthentication yes
KerberosTGTPassing yes
GSSAPIAuthentication yes
GSSAPIDelegateCredentials yes
ssh doesn't forward credentials by default.
> debug3: mm_request_send entering: type 40
> debug3: mm_request_receive entering
> debug3: mm_request_receive_expect entering: type 40
> debug3: mm_request_receive entering
> Failed gssapi for touche from 192.168.2.5 port 24831 ssh2
> debug1: userauth-request for user touche service ssh-connection method
> publickey
> debug1: attempt 2 failures 2
> debug2: input_userauth_request: try method publickey
> debug1: test whether pkalg/pkblob are acceptable
> debug3: mm_key_allowed entering
> debug3: mm_request_send entering: type 20
> debug3: monitor_read: checking request 20
> debug3: mm_answer_keyallowed entering
> debug3: mm_answer_keyallowed: key_from_blob: 0x3c01fa80
> debug1: temporarily_use_uid: 1000/1000 (e=0/0)
> debug1: trying public key file /home/touche/.ssh/authorized_keys
> debug1: restore_uid: 0/0
> debug1: temporarily_use_uid: 1000/1000 (e=0/0)
> debug1: trying public key file /home/touche/.ssh/authorized_keys2
> debug1: restore_uid: 0/0
> debug3: mm_answer_keyallowed: key 0x3c01fa80 is disallowed
> debug3: mm_request_send entering: type 21
> debug3: mm_request_receive entering
> debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED
> debug3: mm_request_receive_expect entering: type 21
> debug3: mm_request_receive entering
> debug2: userauth_pubkey: authenticated 0 pkalg ssh-dss
> Failed publickey for touche from 192.168.2.5 port 24831 ssh2
> debug1: userauth-request for user touche service ssh-connection method
> keyboard-interactive
> debug1: attempt 3 failures 3
> debug2: input_userauth_request: try method keyboard-interactive
> debug1: keyboard-interactive devs
> debug1: auth2_challenge: user=touche devs=
> debug1: kbdint_alloc: devices 'bsdauth'
> debug2: auth2_challenge_start: devices bsdauth
> debug2: kbdint_next_device: devices <empty>
> debug1: auth2_challenge_start: trying authentication method 'bsdauth'
> debug3: mm_bsdauth_query: entering
> debug3: mm_request_send entering: type 12
> debug3: monitor_read: checking request 12
> debug2: bsdauth_query: new bsd auth session
> debug3: bsdauth_query: style <default>
> debug2: bsdauth_query: <empty>
> debug3: mm_answer_bsdauthquery: sending challenge success: 0
> debug3: mm_request_send entering: type 13
> debug3: mm_request_receive entering
> debug3: mm_request_receive_expect entering: type 13
> debug3: mm_request_receive entering
> debug3: mm_bsdauth_query: no challenge
> Failed keyboard-interactive for touche from 192.168.2.5 port 24831 ssh2
> Connection closed by 192.168.2.5
> debug1: Calling cleanup 0x1c01edbc(0x0)
>
> (other logs have not changed)
>
> seems problems stay : "Decrypt integrity check failed"
>
> seems strange also than heimdal log didn't give any failure info ?
>
>
> Regards
>
> Julien