what is the subtle change to sshd such that now VX Connectbot no longer gets any response? VX Connectbot can connect to the bionic sshd just fine, even if it's running on the focal kernel. but gets no response from the focal sshd. what's up with that?
yes meanwhile it works fine to connect to the focal sshd from elsewhere eg from the bionic ssh client. so what's the subtle snub to VX Connectbot?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssh-server 1:8.2p1-4
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu May 7 21:21:26 2020
InstallationDate: Installed on 2020-03-15 (53 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
ProcEnviron:
LC_TIME=en_DK.utf8
TERM=screen
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)
Hi,
this seems to be this upstream issue:
https:/
These things come every now and then, in [1] you see more such being dropped in the past.
Until the client is able to use the newer key exchanges you might need to make your server less secure by adding to /etc/ssh/
KexAlgorithms +diffie-
I think from Ubuntu's POV we are good, we are not changing the default to be less secure but users who want to to so can do that in their local confid.
Marking as invalid since (for your specific case) it appears as a configuration issue (due to the broken client missing the more modern option).
[1]: https:/