Nigel Reed (e9667946) at 17 Mar 09:07
Added vert and cvs as default servers. Added drone rbl as default even though it is added after the fact so user can see it's there.
Nigel Reed (e9667946) at 17 Mar 04:02
ircdcfg would not provide a valid irc.ini file
I setup a new network with one group having SYSOP as the access requirement. My template group has an empty access requirement.
When I set that group as the default template group and did a clone, it added SYSOP to all the groups after it. Now, I cannot change the access requirement using clone. I have to manually go in and clear out the requirement.
I looked into this and I'm just not getting the whole text thing. Not to mention the wiki that mentions gettext doesn't tell you that it's actually something you need to load in and not in the jsobj model.
Since sbbs now supports ssh keys, I'd like to add the ability to add/change keys into the user_defaults.js program. Please add something like AddorChangeSSHKeys "Add or Change SSH Keys" to the text.dat file + whatever else needs to support it.
Closing because it obviously isn't going to happen.
When shutting down the BBS, the services thread does not tell you that it has been terminated.
Mar 3 20:44:15 bbs synchronet: Services thread still running
Mar 3 20:44:25 bbs synchronet: Services thread still running
Mar 3 20:44:35 bbs synchronet: Services thread still running
$ ps -ef|grep sbbs
bbs 1728171 1 4 Mar02 ? 01:15:56 /sbbs/exec/sbbs s! d
bbs 1773863 1352988 0 20:44 pts/0 00:00:00 grep --color=auto sbbs
$
Mar 3 20:44:45 bbs synchronet: Services thread still running
Mar 3 20:44:55 bbs synchronet: Services thread still running
$ ps -ef|grep sbbs
bbs 1773874 1352988 0 20:45 pts/0 00:00:00 grep --color=auto sbbs
$
I received a spam email with a forged date. smbutil shows:
when_written 90ABE044 0000 Fri Nov 30 03:32:52 2046 UTC
and msglist gives the following error when I try to access the message:
!JavaScript msglist.js line 1513: Error: can't convert 2427183172 to an integer
I also have the same problem in DDMsgReader. I expect this is going to be an issue anywhere an external entity is able to forge a date into the far future.
Feb 27 19:47:36 bbs synchronet: term 0030 SSH [192.138.210.158] Attaching to Node 1
Feb 27 19:47:36 bbs synchronet: term Node 1 constructor using socket 30 (settings=8212)
Feb 27 19:47:36 bbs synchronet: term Node 1 temporary file directory: /sbbs/node1/TEMP/
Feb 27 19:47:36 bbs synchronet: term Node 1 passthru listen socket 33 opened
Feb 27 19:47:36 bbs synchronet: term Node 1 passthru socket listening on port 36969
Feb 27 19:47:36 bbs synchronet: term Node 1 passthru connect socket 34 opened
Feb 27 19:47:36 bbs synchronet: term Node 1 input thread started
Feb 27 19:47:36 bbs synchronet: term Node 1 thread started
Feb 27 19:47:36 bbs synchronet: term Node 1 JavaScript: Creating node runtime: 134217728 bytes
Feb 27 19:47:36 bbs synchronet: term Node 1 output thread started
Feb 27 19:47:36 bbs synchronet: term Node 1 outbuf highwater mark tuned to 20000 based on MSS
Feb 27 19:47:36 bbs synchronet: term Node 1 19:47 Tue Feb 27 2024 Node 1
Feb 27 19:47:36 bbs synchronet: term Node 1 SSH bbs.endofthelinebbs.com [192.138.210.158]
Feb 27 19:47:36 bbs synchronet: term Node 1 0030 SSH Setting attribute: SESSINFO_ACTIVE
Feb 27 19:47:39 bbs synchronet: term Node 1 0030 SSH dbg 'No algorithm compatible with the remote system's selection was found: 'ssh-ed25519'' (-50) setting session active
Feb 27 19:47:39 bbs synchronet: term Node 1 SSH login: 'nelgin'
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH Setting attribute: SESSINFO_AUTHRESPONSE
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH Setting attribute: SESSINFO_ACTIVE
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] waiting for channel type.
Feb 27 19:47:39 bbs synchronet: term Node 1 SSH WARNING: attempt to use channel 'shell' (1 != -1 or -1)
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) closing channel
Feb 27 19:47:39 bbs synchronet: term Node 1 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) popping data from input_thread
Feb 27 19:47:39 bbs synchronet: term Node 1 input thread terminated (received 0 bytes in 0 blocks)
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] height 136
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] height 49
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] term: xterm
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> nelgin #1 System password attempt: ''
Feb 27 19:47:39 bbs synchronet: term Node 1 passthru socket disconnected
Feb 27 19:47:39 bbs synchronet: term Node 1 output thread terminated
Feb 27 19:47:40 bbs synchronet: term Node 1 thread terminated (0 node threads remain, 3 clients served)
Feb 27 19:47:40 bbs synchronet: term Node 1 destructor begin
Feb 27 19:47:40 bbs synchronet: term Node 1 JavaScript: Destroying context
Feb 27 19:47:40 bbs synchronet: term Node 1 JavaScript: Destroying runtime
Feb 27 19:47:40 bbs synchronet: term Node 1 destructor end
When I ssh with SyncTerm it connects and then disconnects after a second or two.
I believe this was fixed.
That's chat_sec.js not mrc-client.js then, isn't it?
Could be. I'll bring up a client and leave it running myself and see.
Since sbbs now supports ssh keys, I'd like to add the ability to add/change keys into the user_defaults.js program. Please add something like AddorChangeSSHKeys "Add or Change SSH Keys" to the text.dat file + whatever else needs to support it.
I'm far beyond that commit.
bbs@bbs:~/sbbs-git$ git show
commit 5a45e5c5d91d6b90f734d88f17cf5c09faad26c9 (HEAD -> master, origin/master, origin/HEAD)
Merge: 217700a69 15bbed2b0
Author: Rob Swindell <rob@synchro.net>
Date: Thu Feb 29 09:33:03 2024 +0000
From my logs
Feb 28 03:06:12 bbs synchronet: term Node 2 SSH bbs.endofthelinebbs.com [192.138.210.158]
Feb 28 03:06:12 bbs synchronet: term Node 2 0038 SSH Setting attribute: SESSINFO_ACTIVE
Feb 28 03:06:15 bbs synchronet: term Node 2 0038 SSH dbg 'No algorithm compatible with the remote system's selection was found: 'ssh-ed25519'' (-50) setting session active
Feb 28 03:06:15 bbs synchronet: term Node 2 SSH login: 'nelgin'
Feb 28 03:06:15 bbs synchronet: term Node 2 <nelgin> 0038 SSH Setting attribute: SESSINFO_AUTHRESPONSE
Feb 28 03:06:15 bbs synchronet: term Node 2 <nelgin> 0038 SSH Setting attribute: SESSINFO_ACTIVE
Feb 28 03:06:15 bbs synchronet: term Node 2 <nelgin> 0038 SSH [192.138.210.158] waiting for channel type.
Feb 28 03:06:15 bbs synchronet: term Node 2 <nelgin> SFTP initialized on channel 1
I tried 3 times connecting from the bbs server
$ node status -vaddr
Synchronet Node Display/Control Utility v3.20
Node 1: User #1 at main menu via ssh (MP) [UQ]
addr=47.186.62.206
Node 2: At login prompt
addr=192.138.210.158
Node 3: At login prompt
addr=192.138.210.158
Node 4: At login prompt
addr=192.138.210.158
Node 5: Waiting for connection
Node 6: Waiting for connection
and now I have 3 nodes stuck at login prompt and they have been all night, so not timing out.
netstat is showing just the one connection, which is me on node 1.
root@bbs:~# netstat -anp|grep :22
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1533543/sbbs
tcp 0 0 192.138.210.158:22 47.186.62.206:64636 ESTABLISHED 1533543/sbbs
tcp6 0 0 :::22 :::* LISTEN 1533543/sbbs
Not fixed.
Feb 29 03:49:22 bbs synchronet: term 0030 SSH [47.186.62.206] Connection accepted on 192.138.210.158 port 22 from port 52546
Feb 29 03:49:22 bbs synchronet: term 0030 SSH Cryptlib Session: 14159 created
Feb 29 03:49:22 bbs synchronet: term 0030 SSH [47.186.62.206] Hostname: <no name>
Feb 29 03:49:22 bbs synchronet: term 0030 SSH [47.186.62.206] Attaching to Node 1
Feb 29 03:49:22 bbs synchronet: term Node 1 Loading configuration files from /sbbs/ctrl/
Feb 29 03:49:22 bbs synchronet: term Node 1 constructor using socket 30 (settings=8212)
Feb 29 03:49:22 bbs synchronet: term Node 1 temporary file directory: /sbbs/node1/TEMP/
Feb 29 03:49:22 bbs synchronet: term Node 1 passthru listen socket 33 opened
Feb 29 03:49:22 bbs synchronet: term Node 1 passthru socket listening on port 37101
Feb 29 03:49:22 bbs synchronet: term Node 1 passthru connect socket 34 opened
Feb 29 03:49:22 bbs synchronet: term Node 1 input thread started
Feb 29 03:49:22 bbs synchronet: term Node 1 output thread started
Feb 29 03:49:22 bbs synchronet: term Node 1 outbuf highwater mark tuned to 1436 based on MSS
Feb 29 03:49:22 bbs synchronet: term Node 1 thread started
Feb 29 03:49:22 bbs synchronet: term Node 1 JavaScript: Creating node runtime: 134217728 bytes
Feb 29 03:49:22 bbs synchronet: term Node 1 03:49 Thu Feb 29 2024 Node 1
Feb 29 03:49:22 bbs synchronet: term Node 1 SSH <no name> [47.186.62.206]
Feb 29 03:49:22 bbs synchronet: term Node 1 0030 SSH Setting attribute: SESSINFO_ACTIVE
Feb 29 03:49:24 bbs synchronet: term Node 1 0030 SSH dbg 'No algorithm compatible with the remote system's selection was found: 'ssh-ed25519'' (-50) setting session active
Feb 29 03:49:24 bbs synchronet: term Node 1 SSH login: 'crashtestdummy'
Feb 29 03:49:24 bbs synchronet: term Node 1 <Crashtestdummy> 0030 SSH Setting attribute: SESSINFO_AUTHRESPONSE
Feb 29 03:49:24 bbs synchronet: term Node 1 <Crashtestdummy> 0030 SSH Setting attribute: SESSINFO_ACTIVE
Feb 29 03:49:24 bbs synchronet: term Node 1 <Crashtestdummy> 0030 SSH [47.186.62.206] waiting for channel type.
Feb 29 03:49:24 bbs synchronet: term Node 1 <Crashtestdummy> SFTP initialized on channel 1
sftp session hangs. When I CTRL C it exits but sbbs still has the session hanging.
bbs@bbs:~$ node status -vaddr
Synchronet Node Display/Control Utility v3.20
Node 1: At login prompt
addr=47.186.62.206
Node 2: nelgin viewing node status via ssh (P) [Q]
addr=47.186.62.206
Node 3: Waiting for connection
bbs@bbs:~$ sudo netstat -anp|grep :22
[sudo] password for bbs:
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1583175/sbbs
tcp 0 0 192.138.210.158:22 47.186.62.206:64463 ESTABLISHED 1583175/sbbs
tcp 85 0 192.138.210.158:22 47.186.62.206:52546 CLOSE_WAIT 1583175/sbbs
tcp6 0 0 :::22 :::* LISTEN 1583175/sbbs
Fair enough, in CLOSE_WAIT...15 minutes later...still close wait.
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.
From my logs
Feb 28 03:06:12 bbs synchronet: term Node 2 SSH bbs.endofthelinebbs.com [192.138.210.158]
Feb 28 03:06:12 bbs synchronet: term Node 2 0038 SSH Setting attribute: SESSINFO_ACTIVE
Feb 28 03:06:15 bbs synchronet: term Node 2 0038 SSH dbg 'No algorithm compatible with the remote system's selection was found: 'ssh-ed25519'' (-50) setting session active
Feb 28 03:06:15 bbs synchronet: term Node 2 SSH login: 'nelgin'
Feb 28 03:06:15 bbs synchronet: term Node 2 <nelgin> 0038 SSH Setting attribute: SESSINFO_AUTHRESPONSE
Feb 28 03:06:15 bbs synchronet: term Node 2 <nelgin> 0038 SSH Setting attribute: SESSINFO_ACTIVE
Feb 28 03:06:15 bbs synchronet: term Node 2 <nelgin> 0038 SSH [192.138.210.158] waiting for channel type.
Feb 28 03:06:15 bbs synchronet: term Node 2 <nelgin> SFTP initialized on channel 1
I tried 3 times connecting from the bbs server
$ node status -vaddr
Synchronet Node Display/Control Utility v3.20
Node 1: User #1 at main menu via ssh (MP) [UQ]
addr=47.186.62.206
Node 2: At login prompt
addr=192.138.210.158
Node 3: At login prompt
addr=192.138.210.158
Node 4: At login prompt
addr=192.138.210.158
Node 5: Waiting for connection
Node 6: Waiting for connection
and now I have 3 nodes stuck at login prompt and they have been all night, so not timing out.
netstat is showing just the one connection, which is me on node 1.
root@bbs:~# netstat -anp|grep :22
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1533543/sbbs
tcp 0 0 192.138.210.158:22 47.186.62.206:64636 ESTABLISHED 1533543/sbbs
tcp6 0 0 :::22 :::* LISTEN 1533543/sbbs
Feb 27 19:47:36 bbs synchronet: term 0030 SSH [192.138.210.158] Attaching to Node 1
Feb 27 19:47:36 bbs synchronet: term Node 1 constructor using socket 30 (settings=8212)
Feb 27 19:47:36 bbs synchronet: term Node 1 temporary file directory: /sbbs/node1/TEMP/
Feb 27 19:47:36 bbs synchronet: term Node 1 passthru listen socket 33 opened
Feb 27 19:47:36 bbs synchronet: term Node 1 passthru socket listening on port 36969
Feb 27 19:47:36 bbs synchronet: term Node 1 passthru connect socket 34 opened
Feb 27 19:47:36 bbs synchronet: term Node 1 input thread started
Feb 27 19:47:36 bbs synchronet: term Node 1 thread started
Feb 27 19:47:36 bbs synchronet: term Node 1 JavaScript: Creating node runtime: 134217728 bytes
Feb 27 19:47:36 bbs synchronet: term Node 1 output thread started
Feb 27 19:47:36 bbs synchronet: term Node 1 outbuf highwater mark tuned to 20000 based on MSS
Feb 27 19:47:36 bbs synchronet: term Node 1 19:47 Tue Feb 27 2024 Node 1
Feb 27 19:47:36 bbs synchronet: term Node 1 SSH bbs.endofthelinebbs.com [192.138.210.158]
Feb 27 19:47:36 bbs synchronet: term Node 1 0030 SSH Setting attribute: SESSINFO_ACTIVE
Feb 27 19:47:39 bbs synchronet: term Node 1 0030 SSH dbg 'No algorithm compatible with the remote system's selection was found: 'ssh-ed25519'' (-50) setting session active
Feb 27 19:47:39 bbs synchronet: term Node 1 SSH login: 'nelgin'
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH Setting attribute: SESSINFO_AUTHRESPONSE
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH Setting attribute: SESSINFO_ACTIVE
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] waiting for channel type.
Feb 27 19:47:39 bbs synchronet: term Node 1 SSH WARNING: attempt to use channel 'shell' (1 != -1 or -1)
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) closing channel
Feb 27 19:47:39 bbs synchronet: term Node 1 SSH ERROR 'Cannot close last remaining channel without closing the overall session' (-21) popping data from input_thread
Feb 27 19:47:39 bbs synchronet: term Node 1 input thread terminated (received 0 bytes in 0 blocks)
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] height 136
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] height 49
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> 0030 SSH [192.138.210.158] term: xterm
Feb 27 19:47:39 bbs synchronet: term Node 1 <nelgin> nelgin #1 System password attempt: ''
Feb 27 19:47:39 bbs synchronet: term Node 1 passthru socket disconnected
Feb 27 19:47:39 bbs synchronet: term Node 1 output thread terminated
Feb 27 19:47:40 bbs synchronet: term Node 1 thread terminated (0 node threads remain, 3 clients served)
Feb 27 19:47:40 bbs synchronet: term Node 1 destructor begin
Feb 27 19:47:40 bbs synchronet: term Node 1 JavaScript: Destroying context
Feb 27 19:47:40 bbs synchronet: term Node 1 JavaScript: Destroying runtime
Feb 27 19:47:40 bbs synchronet: term Node 1 destructor end
When I ssh with SyncTerm it connects and then disconnects after a second or two.