RE: OpenSSH_3.5p1 server, PC clients cannot connect

• Previous message: John Mendenhall: "Re: OpenSSH_3.5p1 server, PC clients cannot connect"
• Maybe in reply to: John Mendenhall: "OpenSSH_3.5p1 server, PC clients cannot connect"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

From: Greg Paik <gpaik@smithandhawken.com>
To: "'John Mendenhall'" <john@surfutopia.net>, Greg Paik <gpaik@smithandhawken.com>
Date: Thu, 20 Feb 2003 13:36:01 -0800

Hmm... well, it definitely looks like there's a problem with the ssh
host-key exchange process. Have you checked your host keys on the server to
make sure that the permissions are correct (i.e.- private keys read only for
root, and the pub-keys can be read by all).

Greg

-----Original Message-----
From: John Mendenhall [mailto:john@surfutopia.net]
Sent: Thursday, February 20, 2003 1:18 PM
To: Greg Paik
Cc: secureshell@securityfocus.com
Subject: Re: OpenSSH_3.5p1 server, PC clients cannot connect

Greg,

On Thu, Feb 20, 2003 at 10:56:34AM -0800, Greg Paik wrote:
> Did you upgrade a from a previous version of OpenSSH on the server in
> question?

No. This is a new installation of OpenSSH on this server.

> Also, have you checked the logs on the server side? Or run sshd in debug
> ...

As mentioned in my original post, I am currently running in DEBUG syslog
mode. Here are some additional notes from the logs, and from the client
side:

re: WS_FTP 7.62
client gets message:
  Failed SSH Key Exchange

re: PuTTY
client gets message:
  Fatal: unable to initialise SFTP: could not connect

Client protocol version 2.0; client software version WS_FTP-7.62-2002.12.18
dies immediately after this DEBUG log entry:
  debug1: waiting for SSH2_MSG_NEWKEYS

Client protocol version 2.0; client software version 1.0
  NOTE: I believe this was CuteFTP Pro..., though it could be PuTTY
dies immediately after this DEBUG log entry:
  debug1: waiting for SSH2_MSG_NEWKEYS

Client protocol version 1.99; client software version 1.0
  NOTE: I believe this was PuTTY
appears to startup the sftp-server, but immediately receives a SIGCHLD
signal, indicating client (or server) has quit the sftp-server:
  debug1: subsystem: exec() /usr/local/libexec/sftp-server
  debug1: Received SIGCHLD.

NOTE: I believe CuteFTP appears in the logs the same as WS_FTP,
      thought I could have got PuTTY and CuteFTP logs mixed up.

> Otherwise, are you able to sftp to the server from a UNIX/Linux
> host and run sftp with the "-vvv" options for verbose output?

Yes. Works just fine, as per my message.

Did you want me to include any of the server DEBUG output, or the
`sftp -vvv` output?

> P.S.- What the heck are you doing running SunOS 4.1.4?!?

Legacy system acquired, due for upgrade to OpenBSD or something else later
this year.

Thanks in advance for any pointers you can provide.

JohnM

-- 
John Mendenhall
john@surfutopia.net
surf utopia
internet services

• Next message: Ben Lindstrom: "Re: OpenSSH_3.5p1 server, PC clients cannot connect"
• Previous message: John Mendenhall: "Re: OpenSSH_3.5p1 server, PC clients cannot connect"
• Maybe in reply to: John Mendenhall: "OpenSSH_3.5p1 server, PC clients cannot connect"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]