https://gitlab.synchro.net/main/sbbs/-/issues/727#note_5000
One of my users said that he was unable to login using ssh this morning so no, this does not appear resolved.
```
Feb 28 10:27:24 bbs synchronet: term 0052 SSH [xx.xx.xx.xx] Connection accepted on 192.138.210.158 port 22 from port 44094
Feb 28 10:27:24 bbs synchronet: term 0052 SSH Cryptlib Session: 6028 created Feb 28 10:27:24 bbs synchronet: term 0052 SSH [xx.xx.xx.xx] Hostname: 63-155-65-80.eugn.qwest.net
Feb 28 10:27:24 bbs synchronet: term 0052 SSH [xx.xx.xx.xx] Attaching to Node 5 Feb 28 10:27:24 bbs synchronet: term Node 5 constructor using socket 52 (settings=8212)
Feb 28 10:27:24 bbs synchronet: term Node 5 temporary file directory: /sbbs/node5/TEMP/
Feb 28 10:27:24 bbs synchronet: term Node 5 passthru listen socket 55 opened Feb 28 10:27:24 bbs synchronet: term Node 5 passthru socket listening on port 38835
Feb 28 10:27:24 bbs synchronet: term Node 5 passthru connect socket 56 opened Feb 28 10:27:24 bbs synchronet: term Node 5 output thread started
Feb 28 10:27:24 bbs synchronet: term Node 5 outbuf highwater mark tuned to 1428 based on MSS
Feb 28 10:27:24 bbs synchronet: term Node 5 input thread started
Feb 28 10:27:24 bbs synchronet: term Node 5 thread started
Feb 28 10:27:24 bbs synchronet: term Node 5 JavaScript: Creating node runtime: 134217728 bytes
Feb 28 10:27:24 bbs synchronet: term Node 5 10:27 Wed Feb 28 2024 Node 5
Feb 28 10:27:24 bbs synchronet: term Node 5 SSH xx.xx.xx.xx [xx.xx.xx.xx]
Feb 28 10:27:24 bbs synchronet: term Node 5 0052 SSH Setting attribute: SESSINFO_ACTIVE
Feb 28 10:27:28 bbs synchronet: term Node 5 0052 SSH dbg 'Need resource to proceed' (-50) setting session active
Feb 28 10:27:28 bbs synchronet: term Node 5 SSH login: 'Xuser'
Feb 28 10:27:28 bbs synchronet: term Node 5 <Xuser> 0052 SSH Setting attribute: SESSINFO_AUTHRESPONSE
Feb 28 10:27:28 bbs synchronet: term Node 5 <Xuser> 0052 SSH Setting attribute: SESSINFO_ACTIVE
Feb 28 10:27:28 bbs synchronet: term Node 5 <Xuser> 0052 SSH [xx.xx.xx.xx] waiting for channel type.
Feb 28 10:27:28 bbs synchronet: term Node 5 SSH WARNING: attempt to use channel 'session' (1 != -1 or -1)
Feb 28 10:27:28 bbs synchronet: term Node 5 <Xuser> 0052 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) closing channel
Feb 28 10:27:28 bbs synchronet: term Node 5 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) popping data from input_thread
Feb 28 10:27:28 bbs synchronet: term Node 5 input thread terminated (received 0 bytes in 0 blocks)
Feb 28 10:27:29 bbs synchronet: term Node 5 output thread terminated
Feb 28 10:27:31 bbs synchronet: term Node 5 <Xuser> 0052 SSH [xx.xx.xx.xx] TIMEOUT waiting for channel type.
Feb 28 10:27:31 bbs synchronet: term Node 5 <Xuser> 0052 SSH [xx.xx.xx.xx] session establishment failed
Feb 28 10:27:32 bbs synchronet: term Node 5 thread terminated (4 node threads remain, 329 clients served)
Feb 28 10:27:32 bbs synchronet: term Node 5 destructor begin
Feb 28 10:27:32 bbs synchronet: term Node 5 JavaScript: Destroying context
Feb 28 10:27:32 bbs synchronet: term Node 5 JavaScript: Destroying runtime
```
I have asked him to provide the version of ssh he's using since he's using a linux terminal to connect
$ ssh -l XUser -o pubkeyauthentication=false endofthelinebbs.com
Bencollver@endofthelinebbs.com's password:
Connection to endofthelinebbs.com closed.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)