Okay....well for grins,
1) stop and start (not "restart", actually kill all instances) SSHd on both systems.
NOTE: You might want to make sure you have console access first.
2) Now remove the ~/.ssh directory for your account on both systems (maybe tar it up if you have config information in there)
3) Check the sshd_config and ssh_config for each system.
Get to the "guts" by doing this for each file on each system;
Code:
grep -v "^#" /path/to/sshd_config | grep . | sort
Still nothing out-of-the-ordinary?
Then you're going to have to find out what information is hitting your logs. Suggestion would be to restart the SSHd service with the "verbose" flag, or when you ssh, use "ssh -v
username@hostname"
HOWTO: Be Verbose During SSH
On the Linux Box
Open two terminal windows;
Window #1 "tail -f /var/log/messages"
Window #2 This will be your "SSH" terminal.
On the HP-UX Box
Open two terminal windows;
Window #1 "tail -f /where/your/syslog/logs/stuff"
Window #1 This will be your "SSH" terminal.
Okay, SSH from Linux to HP-UX.
Here's what you should
NOT see;
Code:
luser@linux$ ssh -v luser@hpux
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to hpux [###.###.###.###] port 22.
debug1: Connection established.
debug1: identity file /home/luser/.ssh/identity type -1
debug1: identity file /home/luser/.ssh/id_rsa type -1
debug1: identity file /home/luser/.ssh/id_dsa type -1
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for hpux has changed,
and the key for the according IP address ###.###.###.###
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##.
Please contact your system administrator.
Add correct host key in /home/luser/.ssh/known_hosts to get rid of this message.
Offending key in /home/luser/.ssh/known_hosts:3
RSA host key for hydra has changed and you have requested strict checking.
Host key verification failed.
luser@linux$
This is what you
SHOULD see;
Code:
luser@linux$ ssh -v sysop@hpux
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to hpux [###.###.###.###] port 22.
debug1: Connection established.
debug1: identity file /home/luser/.ssh/identity type -1
debug1: identity file /home/luser/.ssh/id_rsa type -1
debug1: identity file /home/luser/.ssh/id_dsa type -1
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
The authenticity of host 'hpux (###.###.###.###)' can't be established.
RSA key fingerprint is ##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'hydra,192.168.1.120' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Next authentication method: publickey
debug1: Trying private key: /home/luser/.ssh/identity
debug1: Trying private key: /home/luser/.ssh/id_rsa
debug1: Trying private key: /home/luser/.ssh/id_dsa
debug1: Next authentication method: password
luser@hpux's password:
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
Last login: Tue Feb 8 16:47:05 2011
luser@hpux$
