Re: Using/Configuring SSH on Solaris 9 08/03

From: Juan Courcoul (courcoul_at_mac.com)
Date: 11/02/03 

Date: Sun, 02 Nov 2003 01:03:46 -0600

Bigdakine wrote:
>>Subject: Using/Configuring SSH on Solaris 9 08/03
>>From: Juan Courcoul courcoul@mac.com
>>Date: 10/31/03 10:24 AM Hawaiian Standard Time
>>Message-id: <bnugdc$pr21@www.qro.itesm.mx>
>>
>>Is there someplace where I can find info on getting SSH to work on a Solaris
>>9
>>08/03 Sparc machine ?
>>
>>I was happily using SSH on a server with an older version of Sol9. Since it
>>worked ok from the start, never did put any attention on how it was
>>configured. However I recently reinstalled the machine with the latest 08/03
>>release and now, every time I try to connect from a MacOS X workstation, all
>>I
>>get is a:
>>
>> ssh_exchange_identification: Connection closed by remote host
>>
>>and no go. I even tried to running the client that comes with Sol9 on the
>>machine itself and got the same result.
>>
>>Can somebody please point me in the right direction ?
>>
>>Thanks,
>>
>>J. Courcoul
>>
>
>
> Run sshd in debug mode. Then try to connect, and post the output here. It could
> be that your sshd_config file changed with the new installation.
>
> Stuart
> Dr. Stuart A. Weinstein
> Ewa Beach Institute of Tectonics
> "To err is human, but to really foul things up
> requires a creationist"

Ok, tried max debugging and here's the result:

# /usr/lib/ssh/sshd -d -d -d
debug3: cipher ok: aes128-cbc [aes128-cbc,blowfish-cbc,3des-cbc]
debug3: cipher ok: blowfish-cbc [aes128-cbc,blowfish-cbc,3des-cbc]
debug3: cipher ok: 3des-cbc [aes128-cbc,blowfish-cbc,3des-cbc]
debug3: ciphers ok: [aes128-cbc,blowfish-cbc,3des-cbc]
debug2: mac_init: found hmac-sha1
debug3: mac ok: hmac-sha1 [hmac-sha1,hmac-md5]
debug2: mac_init: found hmac-md5
debug3: mac ok: hmac-md5 [hmac-sha1,hmac-md5]
debug3: macs ok: [hmac-sha1,hmac-md5]
debug1: sshd version Sun_SSH_1.0
debug1: Bad RSA1 key file /etc/ssh/ssh_host_rsa_key.
debug1: read SSH2 private key done: name rsa w/o comment success 1
debug1: load_private_key_autodetect: type 1 RSA
debug1: Bad RSA1 key file /etc/ssh/ssh_host_dsa_key.
debug1: read SSH2 private key done: name dsa w/o comment success 1
debug1: load_private_key_autodetect: type 2 DSA
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
debug1: Server will not fork when running in debugging mode.
#

As expected, the process will wait on the "Server listening..." line. When I
try to connect, the "will not fork..." line comes up and the process quits. I
recreated the host DSA and RSA keys, with no success.

Thanks for your help.

J. Courcoul

Relevant Pages

  • Non root scp problem
    ... This is a production web server and the webmaster uses a non-root account to copy files constantly. ... debug1: Connecting to ares port 22. ... invalid collation element ...
    (SSH)
  • Ora-rg could not start using scswitch command!
    ... So oracle server could not be started. ... Is Shockwave Plugin available for Solaris??? ... debug1: read PEM private key done: type RSA ...
    (SunManagers)
  • ssh connect problems (ubuntu feisty client, ubuntu dapper server)
    ... After feisty-upgrade the ssh connect to a dapper server is becoming ... Connection to server closed. ... debug1: Connecting to server port 22. ... debug2: fd 3 setting O_NONBLOCK ...
    (SSH)
  • Login and ssh hang after password, before logging
    ... I have a nice new server, ... I was able to log in through the console and ssh fine ... results for password authentication and public-key authentication: ... debug1: read PEM private key done: type DSA ...
    (alt.linux)
  • Re: Allways prompted for a password
    ... My server is Red Hat ... > Here is the output from a ssh -v -l username servername from my cygwin ... > debug1: Rhosts Authentication disabled, ... on the machine running SSH server you have to allow publickey authorization ...
    (comp.security.ssh)