Hi All,

As you know from the recent post above I am having issues comiling updates to my BBS.

But I am wondering, have there been any recent updates that will fix all the problems with
handshake errors and SSH problems that I am seeing in the logs. I can only assume these are the
result of the recent changes to SSH to overcome the OpenSSL 3.0 vulnerabilities. Syncterm clients still
work fine, but other ssh clients fail with handshake errors. Plus my logs are full of bots trying to
take advantage of the SSL bugs. 8-(

Regards....Geo
oooOOOooo

--------------------------------------
Regards........Geo
oooOOOooo

---
* Synchronet * The Dungeon BBS - Risen from the ashes! - Canberra, Australia
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: SSH errors
By: Digital Man to Keith Matthews on Tue Jun 06 2017 22:41:56

Re: SSH errors
By: Keith Matthews to Digital Man on Wed Jun 07 2017 01:55 pm

Re: SSH errors
By: Digital Man to Geo on Sat Jun 03 2017 13:52:39

Re: SSH errors
By: Geo to All on Fri Apr 28 2017 11:44 am

But I am wondering, have there been any recent updates that will fi all problems with
handshake errors and SSH problems that I am seeing in the logs.

There have been no recent changes in regards to SSH that I'm aware of.

Hi DM,

I guess the changes were really with SSL wern't they. 8-)
I wonder why it is then that when I try and connect with a normal linux s client I get these handshake errors. Syncterm works fine?.

See this new FAQ: http://wiki.synchro.net/faq:tcpip#ssh_kex_algo

digital man

Synchronet/BBS Terminology Definition #46:
SMTP = Simple Message Transfer Protocol
Norco, CA WX: 59.4oF, 91.0% humidity, 6 mph ESE wind, 0.00 inches rain/24hrs

Hi digital man,

Interesting, I tried the suggestions in the FAQ. both the -o option and the Host stanza option on several machines without any change. Unfortunatly they were all Debian systems running versions of OpenSSH V7 (see below). I will try some
other distro's as well. The Centos my BBS is running on has OpenSSH v5 and it is OK.

The -v output recognises that is is diffie-helman-sha256.

Local version string SSH-2.0-OpenSSH_7.5p1 Debian-5
debug1: Remote protocol version 2.0, remote software version cryptlib
debug1: no match: cryptlib
debug1: Authenticating to bbs.barnabasmusic.com:22 as 'geo'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: diffie-hellman-group-exchange-sha256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-cbc MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-cbc MAC: hmac-sha2-256 compression: none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(2048<8192<8192) sent
Received disconnect from 59.167.142.49 port 22:2: Handshake failed
Disconnected from 59.167.142.49 port 22

Prehaps the no match: cryptlib means they have removed it alltogether now?

Thx

--------------------------------------
Regards........Geo
oooOOOooo

---
* Synchronet * The Dungeon BBS - Risen from the ashes! - Canberra, Australia
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: SSH errors
By: Geo to Digital Man on Thu Jul 20 2017 04:13 pm

See this new FAQ: http://wiki.synchro.net/faq:tcpip#ssh_kex_algo

Interesting, I tried the suggestions in the FAQ. both the -o option and the Host stanza option on several machines without any change. Unfortunatly they were all Debian systems running versions of OpenSSH V7 (see below). I will try some
other distro's as well. The Centos my BBS is running on has OpenSSH v5 and it is OK.

If it helps, here's the '-v' output of a successful connection to vert.synchro.net using -o option:

root@cvs:~# ssh -v -oKexAlgorithms=diffie-hellman-group1-sha1 "digital man@vert.synchro.net"
OpenSSH_6.7p1 Debian-5+deb8u3, OpenSSL 1.0.1t 3 May 2016
debug1: Reading configuration data /root/.ssh/config
debug1: /root/.ssh/config line 1: Applying options for vert.synchro.net
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to vert.synchro.net [71.95.196.34] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
<some kruft removed here>
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
debug1: Remote protocol version 2.0, remote software version cryptlib
debug1: no match: cryptlib
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-sha2-256 none
debug1: kex: client->server aes128-cbc hmac-sha2-256 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Server host key: RSA <key>
debug1: Host 'vert.synchro.net' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:10
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: password
debug1: Next authentication method: password


digital man

Synchronet "Real Fact" #69:
You can purchase the BBS Documentary DVD set at http://bbsdocumentary.com/order/
Norco, CA WX: 89.1oF, 42.0% humidity, 6 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.01-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Ditto,

Does anyone know if I do eventually manage to compile the latest code (See my previous post) will that fix
this SSH problem?

Thx.

Hi All,

As you know from the recent post above I am having issues comiling updates to my BBS.

But I am wondering, have there been any recent updates that will fix all the problems with
handshake errors and SSH problems that I am seeing in the logs. I can only assume these are the
result of the recent changes to SSH to overcome the OpenSSL 3.0 vulnerabilities. Syncterm clients still
work fine, but other ssh clients fail with handshake errors. Plus my logs are full of bots trying to
take advantage of the SSL bugs. 8-(

Regards....Geo
oooOOOooo

--------------------------------------
Regards........Geo
oooOOOooo

--------------------------------------
Regards........Geo
oooOOOooo

---
* Synchronet * The Dungeon BBS - Risen from the ashes! - Canberra, Australia
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: SSH errors
By: Geo to All on Fri Apr 28 2017 11:44 am

But I am wondering, have there been any recent updates that will fix all the problems with
handshake errors and SSH problems that I am seeing in the logs.

There have been no recent changes in regards to SSH that I'm aware of.


digital man

Synchronet/BBS Terminology Definition #37:
NUP = New User Password
Norco, CA WX: 84.0oF, 46.0% humidity, 16 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: SSH errors
By: Digital Man to Geo on Sat Jun 03 2017 13:52:39

Re: SSH errors
By: Geo to All on Fri Apr 28 2017 11:44 am

But I am wondering, have there been any recent updates that will fix all problems with
handshake errors and SSH problems that I am seeing in the logs.

There have been no recent changes in regards to SSH that I'm aware of.

Hi DM,

I guess the changes were really with SSL wern't they. 8-)
I wonder why it is then that when I try and connect with a normal linux ssh client I get these handshake errors. Syncterm works fine?.

I have had some of my users mention the problem to me as well. Could be the SSL library in CENTOS I guess?


--------------------------------------
Regards........Geo
oooOOOooo
--- SBBSecho 2.27-Linux
* Origin: The Dungeon BBS, Canberra, Australia (3:712/620)

Re: SSH errors
By: Keith Matthews to Digital Man on Wed Jun 07 2017 01:55 pm

Re: SSH errors
By: Digital Man to Geo on Sat Jun 03 2017 13:52:39

Re: SSH errors
By: Geo to All on Fri Apr 28 2017 11:44 am

But I am wondering, have there been any recent updates that will fix all problems with
handshake errors and SSH problems that I am seeing in the logs.

There have been no recent changes in regards to SSH that I'm aware of.

Hi DM,

I guess the changes were really with SSL wern't they. 8-)
I wonder why it is then that when I try and connect with a normal linux ssh client I get these handshake errors. Syncterm works fine?.

See this new FAQ: http://wiki.synchro.net/faq:tcpip#ssh_kex_algo

digital man

Synchronet/BBS Terminology Definition #46:
SMTP = Simple Message Transfer Protocol
Norco, CA WX: 59.4oF, 91.0% humidity, 6 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: SSH errors
By: Digital Man to Keith Matthews on Tue Jun 06 2017 22:41:56

Re: SSH errors
By: Keith Matthews to Digital Man on Wed Jun 07 2017 01:55 pm

Re: SSH errors
By: Digital Man to Geo on Sat Jun 03 2017 13:52:39

Re: SSH errors
By: Geo to All on Fri Apr 28 2017 11:44 am

But I am wondering, have there been any recent updates that will fi all problems with
handshake errors and SSH problems that I am seeing in the logs.

There have been no recent changes in regards to SSH that I'm aware of.

Hi DM,

I guess the changes were really with SSL wern't they. 8-)
I wonder why it is then that when I try and connect with a normal linux s client I get these handshake errors. Syncterm works fine?.

See this new FAQ: http://wiki.synchro.net/faq:tcpip#ssh_kex_algo

Thx DM 8-)

--------------------------------------
Regards........Geo
oooOOOooo

---
* Synchronet * The Dungeon BBS - Risen from the ashes! - Canberra, Australia
* Origin: Vertrauen - vert.synchro.net (1:103/705)