Re: ssh-keyscan exits in mid-way

Hi all,

Detailed debug traces of "ssh-keyscan" is given below.

# ssh-keyscan -vvv -t rsa host.server.com
debug2: fd 3 setting O_NONBLOCK
debug1: no match: mpSSH_0.1.0
# host.server.com SSH-2.0-mpSSH_0.1.0
debug1: Enabling compatibility mode for protocol 2.0
debug3: RNG is ready, skipping seeding
debug1: SSH2_MSG_KEXINIT sent
Received disconnect from 15.244.96.225: 11: SSH Disabled


--
M.P

----- Original Message -----
From: "ponraj" <tryponraj@gmail.com>
To: "Damien Miller" <djm@mindrot.org>
Cc: <openssh-unix-dev@mindrot.org>
Sent: Wednesday, July 19, 2006 2:37 PM
Subject: Re: ssh-keyscan exits in mid-way


> Hi all,
>
> Debug trace is given below.
>
> # ssh-keyscan -vvv host.server.com
> debug2: fd 3 setting O_NONBLOCK
> debug1: no match: mpSSH_0.1.0
> debug1: host.server.com doesn't support ssh1
>
> # ssh -vvv host.server.com
> OpenSSH_4.3p2-hpn, OpenSSL 0.9.7i 14 Oct 2005
> HP-UX Secure Shell-A.04.30.005, HP-UX Secure Shell version
> debug1: Reading configuration data /opt/ssh/etc/ssh_config
> debug3: RNG is ready, skipping seeding
> debug2: ssh_connect: needpriv 0
> debug1: Connecting to host.server.com [15.244.96.225] port 22.
> debug1: Connection established.
> debug1: permanently_set_uid: 0/3
> debug1: identity file /.ssh/identity type 0
> debug3: Not a RSA1 key file /.ssh/id_rsa.
> debug2: key_type_from_name: unknown key type '-----BEGIN'
> debug3: key_read: missing keytype
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug2: key_type_from_name: unknown key type '-----END'
> debug3: key_read: missing keytype
> debug1: identity file /.ssh/id_rsa type 1
> debug3: Not a RSA1 key file /.ssh/id_dsa.
> debug2: key_type_from_name: unknown key type '-----BEGIN'
> debug3: key_read: missing keytype
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug2: key_type_from_name: unknown key type '-----END'
> debug3: key_read: missing keytype
> debug1: identity file /.ssh/id_dsa type 2
> debug1: Remote protocol version 2.0, remote software version mpSSH_0.1.0
> debug1: no match: mpSSH_0.1.0
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_4.3p2-hpn
> debug2: fd 4 setting O_NONBLOCK
> debug3: RNG is ready, skipping seeding
> debug1: SSH2_MSG_KEXINIT sent
> Received disconnect from 15.244.96.225: 11: SSH Disabled
>
>
> --
> M.P
>
> ----- Original Message -----
> From: "Damien Miller" <djm@mindrot.org>
> To: "ponraj" <tryponraj@gmail.com>
> Cc: <openssh-unix-dev@mindrot.org>
> Sent: Wednesday, July 19, 2006 10:23 AM
> Subject: Re: ssh-keyscan exits in mid-way
>
>
>> On Wed, 19 Jul 2006, ponraj wrote:
>>
>>> I digged up this problem further and find my results below.
>>>
>>> ssh-keyscan ignores the hosts if they are not up or sshd is not
>>> running when used with -f <file> option. But when it encounters any
>>> error while retrieving the host key from the machine which is up and
>>> have sshd running, it simply exits. This may happen due to transport
>>> layer implementation in packet.c at packet_read_poll_seqnr() which
>>> results in exiting.
>>>
>>> My guess is that as packet.c is utilised by all OpenSSH utilities
>>> including ssh-keyscan, we can't make ssh-keyscan to continue with
>>> remaining hosts as specified in -f <files> in case of an error. But I
>>> also vote for atleast documenting this one.
>>
>> ssh-keyscan could probably do with a cleanup_exit() implementation
>> that looks at nonfatal_fatal, like its fatal() implmenetation does.
>> This would obviously need to be done carefully.
>>
>> By the way, when you report problems please include debug traces. Saying
>> that "ssh-keyscan exits in mid-way" doesn't give enough information
>> for anyone to help you. Posting a debug trace from "ssh-keyscan -vvv"
>> would.
>>
>> -d
>>
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev@mindrot.org
> http://lists.mindrot.org/mailman/lis...enssh-unix-dev
>
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@mindrot.org
http://lists.mindrot.org/mailman/lis...enssh-unix-dev