Server authentication none fails to connect

[Mick]

On Saturday 25 Feb 2017 10:59:43 Mick wrote:
> Hi All,
> 
> I am trying to understand why openssh client started failing to establish a
> connection.  The client is running on Mint Linux and was able to connect to
> this server until recently without problems.  Now when it tries to connect
> (using sftp), it fails like so:
> 
> $ sftp -v user_name at host_name.netsolhost.com:/
> OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
> [snip ...]
> 
> debug1: Host 'account_name.netsolhost.com' is known and matches the RSA host
> key.
> debug1: Found key in /home/mick/.ssh/known_hosts:1
> debug1: rekey after 4294967296 blocks
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug1: rekey after 4294967296 blocks
> debug1: SSH2_MSG_NEWKEYS received
> debug1: Authentication succeeded (none).
> Authenticated to account_name.netsolhost.com ([206.188.193.57]:22).
> debug1: channel 0: new [client-session]
> debug1: Entering interactive session.
> debug1: pledge: network
> debug1: channel 0: free: client-session, nchannels 1
> debug1: fd 0 clearing O_NONBLOCK
> Connection to account_name.netsolhost.com closed by remote host.
> Transferred: sent 1560, received 1992 bytes, in 0.0 seconds
> Bytes per second: sent 18334897.2, received 23412253.3
> debug1: Exit status -1
> Couldn't read packet: Connection reset by peer
> 
> 
> What is the meaning of the message: "Authentication succeeded (none)."?
> 
> Shouldn't the server respond with a list of authentication method names, and
> authentications that can continue, including as in the past "password"?

Only to add:  a connection from the same PC with Filezilla succeeds as it 
always has done, but I am guessing Filezilla perhaps ships with a different 
ssh client.
-- 
Regards,
Mick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20170225/3437cd23/attachment.bin>