SSH Can't connect to one raspberry pi but can to another

Help and Support Raspberry Pi
1

Hi, I have 2 raspberry pi 2’s with OSMC july 2018
Using Winscp on PC I can connect to both of them.
Using es file explorer on phone I can only connect to one of them.

I found this on the internet about adding IPQoS cs0 cs0
to /etc/ssh/sshd_config
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=138631&sid=1e9c11565b9ffec260fa96ca48009edd&start=100

I got permission denied trying to edit the file so I compared the file on both raspberry pi’s and noticed they are completelly different.

Any idea why they are different? and which should be the correct one? (I’m guesseing RPI One)
Also how can I copy the correct one over without getting permission denied in winscp.

edit: not sure why some text has gone massive.

RPI One - Can connect through es file explorer (Text at start of file)

$OpenBSD: sshd_config,v 1.100 2016/08/15 12:32:04 naddy Exp $

This is the sshd server system-wide configuration file. See

sshd_config(5) for more information.

This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

The strategy used for options in the default sshd_config shipped with

OpenSSH is to specify options with their default value where

possible, but leave them commented. Uncommented options override the

default value.

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
(can’t post the rest as new user link limit)

RPI Two - Can’t connect (Text at start of file)

Package generated configuration file

See the sshd_config(5) manpage for details

What ports, IPs and protocols we listen for

Port 22

Use these options to restrict which interfaces/protocols sshd will bind to

#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2

HostKeys for protocol version 2

HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation sandbox

2

I assume your es file explorer uses old key exchange.
Check this thread for details.

3

Thanks, I’ve emailed the developer of es file explorer and asked if there’s an update coming for it.

I looked at the dates of the files in the ssh folders and it’s strange that some are newer on the box that connects and some are newer on the box that doesn’t connect, one box has ucf file and other has dpkg.

I’m thinking the difference is probably caused by updating them at different times? I skipped a few months sometimes.

Box can connect | sshd_config 18/11/2017 | sshd_config.dpkg-dist 17/05/2017 | ssh_config 18/11/2017 | keys 13/03/2016

Box can’t connect | sshd_config 17/05/2017 | sshd_config.ucf-dist 13/02/2018 | ssh_config 18/11/2017 | keys 01/01/1970

4

Well there could be several reasons for that.
Anyhow the correct box is the one you can not connect to and it should have this section in there. So unless you want to make both accessable by current version of es file explorer (unsecure) I suggest to copy the sshd_config from the working to the non working

Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation sandbox
5

Ok thanks for the help
I’ll probably copy the code over and see if there’s a different android app that supports the new key exchange until es file explorer is updated.