On 9/24/05, Simon Strandgaard <[EMAIL PROTECTED]> wrote:
> I have openbsd 3.7 on an old P133.
> Connecting with SSH to the box takes near 20 seconds.
>
>
> Any ideas on how to make it go faster?
>

just realized that ssh takes a '-v' argument.. output attached.


approx 13 seconds is spend in this line:
debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1+CAN-2004-0175


any ideas how to make this error go away?

--
Simon Strandgaard


prompt> ssh -v [EMAIL PROTECTED]
OpenSSH_3.6.1p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090707f
debug1: Reading configuration data /etc/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: Connecting to 192.168.1.123 [192.168.1.123] port 22.
debug1: Connection established.
debug1: identity file /Users/simonstrandgaard/.ssh/identity type -1
debug1: identity file /Users/simonstrandgaard/.ssh/id_rsa type 1
debug1: identity file /Users/simonstrandgaard/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_4.1
debug1: match: OpenSSH_4.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1+CAN-2004-0175
debug1: An invalid name was supplied
Cannot determine realm for numeric host address

debug1: An invalid name was supplied
A parameter was malformed
Validation error

debug1: An invalid name was supplied
Cannot determine realm for numeric host address

debug1: An invalid name was supplied
A parameter was malformed
Validation error

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 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
debug1: Host '192.168.1.123' is known and matches the RSA host key.
debug1: Found key in /Users/simonstrandgaard/.ssh/known_hosts:7
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,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/simonstrandgaard/.ssh/identity
debug1: Offering public key: /Users/simonstrandgaard/.ssh/id_rsa
debug1: Authentications that can continue:
publickey,password,keyboard-interactive
debug1: Offering public key: /Users/simonstrandgaard/.ssh/id_dsa
debug1: Server accepts key: pkalg ssh-dss blen 433 lastkey 0x300b80 hint 2
debug1: read PEM private key done: type DSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: channel 0: request pty-req
debug1: channel 0: request shell
debug1: channel 0: open confirm rwindow 0 rmax 32768
Last login: Sat Sep 24 12:26:40 2005 from 192.168.1.2
OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005

Welcome to OpenBSD: The proactively secure Unix-like operating system.

Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code.  With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.

I had to hit him -- he was starting to make sense.
molly:neoneye {98}

Reply via email to