Main issueshttps://gitlab.synchro.net/groups/main/-/issues2024-03-22T07:20:15Zhttps://gitlab.synchro.net/main/sbbs/-/issues/616scfg: ^v doesn't paste in Transfer Protocols sections2024-03-22T07:20:15ZNigel Reedscfg: ^v doesn't paste in Transfer Protocols sectionsUsing ^C then ^V to copy and paste an entry in the File Options > Transfer Protocols section doesn't work. The same process works fine when cutting & pasting in the file directories area.Using ^C then ^V to copy and paste an entry in the File Options > Transfer Protocols section doesn't work. The same process works fine when cutting & pasting in the file directories area.Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/612incorrect variable replacement in node_action causes core dump2023-09-02T21:06:01ZNigel Reedincorrect variable replacement in node_action causes core dump~~~
bbs.replace_text(708,"%s at Multi Relay Chat %s");
bbs.node_action = NODE_BXFR;
bbs.nodesync();
bbs.revert_text(708);
...~~~
bbs.replace_text(708,"%s at Multi Relay Chat %s");
bbs.node_action = NODE_BXFR;
bbs.nodesync();
bbs.revert_text(708);
bbs.exec("?../xtrn/mrc/mrc-client.js",null,"/sbbs/xtrn/mrc/");
~~~
I was trying to get "via ssh" on the end of the Multi Relay Chat line, adding a %s would cause the terminal to core dump
~~~
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type <RET> for more, q to quit, c to continue without paging--c
Core was generated by `/sbbs/exec/sbbs d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/strlen-vec.S:126
126 ../sysdeps/x86_64/multiarch/strlen-vec.S: No such file or directory.
[Current thread is 1 (Thread 0x7ff1527fc640 (LWP 1052439))]
(gdb) bt
#0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/strlen-vec.S:126
#1 0x00007ff1c7c1cdb1 in __vfprintf_internal (s=s@entry=0x7ff1527f01a0, format=format@entry=0x7ff14816de70 "%s at Multi Relay Chat %s",
ap=ap@entry=0x7ff1527f02e0, mode_flags=mode_flags@entry=0) at ./stdio-common/vfprintf-internal.c:1517
#2 0x00007ff1c7c27a09 in __vsprintf_internal (string=0x7ff1527f04e0 "Nelgin at Multi Relay Chat ", maxlen=maxlen@entry=18446744073709551615,
format=0x7ff14816de70 "%s at Multi Relay Chat %s", args=args@entry=0x7ff1527f02e0, mode_flags=mode_flags@entry=0) at ./libio/iovsprintf.c:95
#3 0x00007ff1c7c069a8 in __sprintf (s=<optimized out>, format=<optimized out>) at ./stdio-common/sprintf.c:30
#4 0x00007ff1c810dab3 in sbbs_t::putnodedat (this=0x7ff1b4503ac0, number=1, node=0x7ff1b450f7b0) at putnode.cpp:51
#5 0x00007ff1c7fe9640 in sbbs_t::nodesync (this=0x7ff1b4503ac0, clearline=false) at getnode.cpp:126
#6 0x00007ff1c7ffce2d in js_nodesync (cx=0x7ff14806e6e0, argc=0, arglist=0x7ff1600000a0) at js_bbs.cpp:1282
#7 0x00007ff1c84480c7 in js::CallJSNative (vp=0x7ff1600000a0, argc=0, native=0x7ff1c7ffccbc <js_nodesync(JSContext*, uintN, jsval*)>,
cx=0x7ff14806e6e0) at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jscntxtinlines.h:701
#8 js::Interpret (cx=0x7ff14806e6e0, entryFrame=0x7ff160000048, inlineCallCount=0, interpMode=JSINTERP_NORMAL) at jsinterp.cpp:4799
#9 0x00007ff1c823a5c6 in js::RunScript (cx=0x7ff14806e6e0, script=0x7ff1481eeea0, fp=0x7ff160000048)
at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsinterp.cpp:653
#10 0x00007ff1c823d55f in js::Execute (cx=0x7ff14806e6e0, chain=0x7ff15169ac60, script=0x7ff1481eeea0, prev=0x0, flags=0, result=0x7ff1527f5078)
at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsinterp.cpp:1028
#11 0x00007ff1c819e3a1 in JS_ExecuteScript (cx=0x7ff14806e6e0, obj=0x7ff15169ac60, scriptObj=0x7ff15169aca8, rval=0x7ff1527f5078) at jsapi.cpp:4998
#12 0x00007ff1c7fc1971 in sbbs_t::js_execfile (this=0x7ff1b4503ac0, cmd=0x7ff1527fa920 "eotl_chat", startup_dir=0x0, scope=0x0,
js_cx=0x7ff14806e6e0, js_glob=0x7ff151603048) at exec.cpp:676
#13 0x00007ff1c7fc2014 in sbbs_t::exec_bin (this=0x7ff1b4503ac0, cmdline=0x7ff1527fa920 "eotl_chat", csi=0x7ff1b4515d98, startup_dir=0x0)
at exec.cpp:770
#14 0x00007ff1c7fc43ef in sbbs_t::exec (this=0x7ff1b4503ac0, csi=0x7ff1b4515d98) at exec.cpp:1331
#15 0x00007ff1c80e2938 in node_thread (arg=0x7ff1b4503ac0) at main.cpp:4305
#16 0x00007ff1c7c3ab43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#17 0x00007ff1c7ccca00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
~~~
As a follow up, what would the proper value be to include "via ssh" or "via telnet" ?Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/611js.exec caused core jump2024-03-22T07:20:15ZNigel Reedjs.exec caused core jumpin my chat javascript menu file
js.exec("../xtrn/mrc/mrc-client.js",null,"/sbbs/xtrn/mrc/");
I had just changed bbs.exec to js.exec without checking the parameters.
~~~
[Thread debugging using libthread_db enabled]
Using host libthre...in my chat javascript menu file
js.exec("../xtrn/mrc/mrc-client.js",null,"/sbbs/xtrn/mrc/");
I had just changed bbs.exec to js.exec without checking the parameters.
~~~
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type <RET> for more, q to quit, c to continue without paging--c
Core was generated by `/sbbs/exec/sbbs d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f7f5883fdd6 in JSObject::getClass (this=0x0) at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsobj.h:427
427 /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsobj.h: No such file or directory.
[Current thread is 1 (Thread 0x7f7ee09fd640 (LWP 984457))]
(gdb) bt
#0 0x00007f7f5883fdd6 in JSObject::getClass (this=0x0) at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsobj.h:427
#1 0x00007f7f5883fdf8 in JSObject::getOps (this=0x0) at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsobj.h:435
#2 0x00007f7f588401d0 in JSObject::defineProperty (this=0x0, cx=0x7f7ed406e6e0, id=140182618251712, value=..., getter=0x0, setter=0x0, attrs=3)
at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsobj.h:1223
#3 0x00007f7f58836e1a in DefinePropertyById (cx=0x7f7ed406e6e0, obj=0x0, id=140182618251712, value=..., getter=0x0, setter=0x0, attrs=3, flags=0,
tinyid=0) at jsapi.cpp:3420
#4 0x00007f7f58837055 in DefineProperty (cx=0x7f7ed406e6e0, obj=0x0, name=0x7f7f58c7d370 "argv", value=..., getter=0x0, setter=0x0, attrs=3,
flags=0, tinyid=0) at jsapi.cpp:3457
#5 0x00007f7f588370d9 in JS_DefineProperty (cx=0x7f7ed406e6e0, obj=0x0, name=0x7f7f58c7d370 "argv", value=18445617618932470848, getter=0x0,
setter=0x0, attrs=3) at jsapi.cpp:3464
#6 0x00007f7f586fed5d in js_execfile (cx=0x7f7ed406e6e0, argc=3, arglist=0x7f7ecf3ff0a0) at js_internal.c:407
#7 0x00007f7f58ae60c7 in js::CallJSNative (vp=0x7f7ecf3ff0a0, argc=3, native=0x7f7f586fdff3 <js_execfile>, cx=0x7f7ed406e6e0)
at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jscntxtinlines.h:701
#8 js::Interpret (cx=0x7f7ed406e6e0, entryFrame=0x7f7ecf3ff048, inlineCallCount=0, interpMode=JSINTERP_NORMAL) at jsinterp.cpp:4799
#9 0x00007f7f588d85c6 in js::RunScript (cx=0x7f7ed406e6e0, script=0x7f7ed417b8a0, fp=0x7f7ecf3ff048)
at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsinterp.cpp:653
#10 0x00007f7f588db55f in js::Execute (cx=0x7f7ed406e6e0, chain=0x7f7ecf29ac18, script=0x7f7ed417b8a0, prev=0x0, flags=0, result=0x7f7ee09f6078)
at /home/bbs/sbbs-test/repo/3rdp/src/mozjs/js-1.8.5/js/src/jsinterp.cpp:1028
#11 0x00007f7f5883c3a1 in JS_ExecuteScript (cx=0x7f7ed406e6e0, obj=0x7f7ecf29ac18, scriptObj=0x7f7ecf29ad80, rval=0x7f7ee09f6078) at jsapi.cpp:4998
#12 0x00007f7f5865f971 in sbbs_t::js_execfile (this=0x7f7f485bf9a0, cmd=0x7f7ee09fb920 "eotl_chat", startup_dir=0x0, scope=0x0,
js_cx=0x7f7ed406e6e0, js_glob=0x7f7ecf203048) at exec.cpp:676
#13 0x00007f7f58660014 in sbbs_t::exec_bin (this=0x7f7f485bf9a0, cmdline=0x7f7ee09fb920 "eotl_chat", csi=0x7f7f485d1c78, startup_dir=0x0)
at exec.cpp:770
#14 0x00007f7f586623ef in sbbs_t::exec (this=0x7f7f485bf9a0, csi=0x7f7f485d1c78) at exec.cpp:1331
#15 0x00007f7f58780938 in node_thread (arg=0x7f7f485bf9a0) at main.cpp:4305
#16 0x00007f7f582d8b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#17 0x00007f7f5836aa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
~~~
Let me know if you need anything else.Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/609Add ability to view ip addresses with node &nodelist.js2023-09-01T00:42:20ZNigel ReedAdd ability to view ip addresses with node &nodelist.jsIt may be useful for the sysop to view IP addresses for the nodes that are connecting or connected via the node or nodelist.js utilities.
As discussed on irc, please add this ability for sysop users.It may be useful for the sysop to view IP addresses for the nodes that are connecting or connected via the node or nodelist.js utilities.
As discussed on irc, please add this ability for sysop users.Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/607MRC client crashes with error - !JavaScript inputline.js line 150: Error: Inf...2024-03-02T02:14:09ZKeyop TroyMRC client crashes with error - !JavaScript inputline.js line 150: Error: Infinite loop (864001 operation callbacks) detectedAfter running MRC client for several hours, I get this error message which aborts the MRC client.
!JavaScript inputline.js line 150: Error: Infinite loop (864001 operation callbacks) detectedAfter running MRC client for several hours, I get this error message which aborts the MRC client.
!JavaScript inputline.js line 150: Error: Infinite loop (864001 operation callbacks) detectedhttps://gitlab.synchro.net/main/sbbs/-/issues/606scfg from xtrn menu hangs2023-08-30T20:33:12ZNigel Reedscfg from xtrn menu hangsExecuting external: /sbbs/exec/scfg -iA -l24
However when the menu pops up, it doesn't respond to any key presses, including escape, so I have to disconnect.
[prog:PROGS:SCFGANSI]
name=Synchronet Configuration (ANSI)
ars=SYSOP AND ANSI...Executing external: /sbbs/exec/scfg -iA -l24
However when the menu pops up, it doesn't respond to any key presses, including escape, so I have to disconnect.
[prog:PROGS:SCFGANSI]
name=Synchronet Configuration (ANSI)
ars=SYSOP AND ANSI
execution_ars=
type=0
settings=0x4004
event=0
cost=0
cmd=%!scfg%. -iA -l%r
clean_cmd=
startup_dir=
textra=0
max_time=0
max_inactivity=0https://gitlab.synchro.net/main/sbbs/-/issues/604MQTT subscriptions stop working after broker restarts2023-09-01T01:29:07ZRick ParrishMQTT subscriptions stop working after broker restartsIf the MQTT broker restarts while Synchronet is running, then the subscriptions that should handle sbbs/+/node/+/input, sbbs/+/host/+/server/term/recycle, etc, stop working.
From the bit I've read, it seems like two suggested solutions ...If the MQTT broker restarts while Synchronet is running, then the subscriptions that should handle sbbs/+/node/+/input, sbbs/+/host/+/server/term/recycle, etc, stop working.
From the bit I've read, it seems like two suggested solutions are:
1) Don't use clean sessions, so subscriptions are remembered after reconnecting, or
2) Move subscription calls to the connect callback, so they're re-subscribed after reconnectingRob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/603[hit a key] when spying.2024-03-22T07:20:13ZNigel Reed[hit a key] when spying.I'm not sure if this is a feature or a bug.
When you spy on a node and that node comes to a [hit a key] prompt, it also requires that the spying node hit a key. This doesn't seem right, unless it's to allow the spying node to read what'...I'm not sure if this is a feature or a bug.
When you spy on a node and that node comes to a [hit a key] prompt, it also requires that the spying node hit a key. This doesn't seem right, unless it's to allow the spying node to read what's on the page before continuing. I wouldn't expect that to be the correct behavior though. It could lead to accidental key input on the spied upon node.Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/602Default file area data directory not sticking2024-03-22T07:20:13ZNigel ReedDefault file area data directory not stickingscfg > File Area > (pick an area) > Directory Defaults > Data Directory
Enter a new directory ../data/dirs/tqwnet/ in my case hit enter.
Escape 3 times, save, escape confirm exit.
Rerun scfg, go back to the same location. Data director...scfg > File Area > (pick an area) > Directory Defaults > Data Directory
Enter a new directory ../data/dirs/tqwnet/ in my case hit enter.
Escape 3 times, save, escape confirm exit.
Rerun scfg, go back to the same location. Data directory will be back at [../data/dirs/]https://gitlab.synchro.net/main/sbbs/-/issues/601IRC command /users causes ircd to crash2024-03-22T07:20:15ZKeyop TroyIRC command /users causes ircd to crashIssuing the "/users" command during a Synchronet IRC session causes ircd to crash with the same effect/errors as Nelgin's #402 issue.
Aug 17 18:41:33 lr08 jsexec[938184]: SynchronetIRCd-1.10 started.
Aug 17 18:41:33 lr08 jsexec[938184]...Issuing the "/users" command during a Synchronet IRC session causes ircd to crash with the same effect/errors as Nelgin's #402 issue.
Aug 17 18:41:33 lr08 jsexec[938184]: SynchronetIRCd-1.10 started.
Aug 17 18:41:33 lr08 jsexec[938184]: Trying to read configuration from: /sbbs/ctrl/ircd.conf
Aug 17 18:41:33 lr08 jsexec[938184]: 0013 !ERROR 98 binding IRCd socket to port 6667: Address already in use
Aug 17 18:41:33 lr08 jsexec[938184]: !Error Error: Unable to add host to socket set creating listening socket on port 6667
Aug 17 18:41:33 lr08 jsexec[938184]: !Module (/sbbs/exec/ircd.js) set exit_code: 1
Aug 17 18:41:33 lr08 jsexec[938184]: #012Re-running: /sbbs/exec/ircd.jshttps://gitlab.synchro.net/main/sbbs/-/issues/600mqtt: Add configuration setting for websocket port2023-08-13T01:10:12ZRick Parrishmqtt: Add configuration setting for websocket portA browser-based node spy will need to connect to the mqtt broker using websockets, so a second "Broker Websocket Port" or "Broker WSS Port" setting will be needed to support this.
Would it make sense to include in SCFG and store in main...A browser-based node spy will need to connect to the mqtt broker using websockets, so a second "Broker Websocket Port" or "Broker WSS Port" setting will be needed to support this.
Would it make sense to include in SCFG and store in main.ini? Or since this could be considered an optional feature, maybe it would make more sense as a modopts.ini setting instead?
EDIT: I guess there should actually be separate settings for WS and WSS ports, so sysops who haven't setup TLS can still make use of the node spy.
So I'd lean towards specifying the websocket ports via modopts.ini, which keeps the SCFG screen to the minimum needed for mqtt to work.
Then if/when someone loads the node spy, I'll have it output instructions on how to specify the websocket ports in modopts.ini.Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/597Check mqtt node for missing value2023-08-06T18:40:28ZNigel ReedCheck mqtt node for missing valueCan you check this node is correct? There's no value for served.
sbbs/EOTLBBS/host/bbs.endofthelinebbs.com/server/web : msg.payload : string[34]
"ready 23/150 clients 34805 served "
This one seems ok.
sbbs/EOTLBBS/host/bbs.endoftheli...Can you check this node is correct? There's no value for served.
sbbs/EOTLBBS/host/bbs.endofthelinebbs.com/server/web : msg.payload : string[34]
"ready 23/150 clients 34805 served "
This one seems ok.
sbbs/EOTLBBS/host/bbs.endofthelinebbs.com/server/web/served : msg.payload : number
34805Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/590IRC - stop trying to autoconnect when connected2023-10-24T01:01:36ZNigel ReedIRC - stop trying to autoconnect when connectedTwo issues here.
I was connected to vert. It's my only C/N lines.
vert went down and my ircd kept trying to autoconnect.
I changed the C/N lines to use cvs and commented out vert then rehashed.
Once connected to cvs, my ircd is consta...Two issues here.
I was connected to vert. It's my only C/N lines.
vert went down and my ircd kept trying to autoconnect.
I changed the C/N lines to use cvs and commented out vert then rehashed.
Once connected to cvs, my ircd is constantly trying to also connect to vert.
so these need fixing.
1. Do not try to connect to another server when already connected. This may be unique to my situation since I'm pretending to be a hub for services.
2. Is a server isn't in the ircd after a rehash, the ircd shouldn't try to be connecting to it.https://gitlab.synchro.net/main/sbbs/-/issues/589DDAreaChooer fails with area and no subboards2023-07-20T18:20:34ZNigel ReedDDAreaChooer fails with area and no subboardsI deleted a couple of subboards earlier today. Now when I use my menu option "J" to jump to a new area, I'm told "There are no sub-boards in Sysop's Test Groups." and it goes back to the menu.
It should probably silently ignore empty ar...I deleted a couple of subboards earlier today. Now when I use my menu option "J" to jump to a new area, I'm told "There are no sub-boards in Sysop's Test Groups." and it goes back to the menu.
It should probably silently ignore empty areas and not display them as not to cause issues changing to a new area.Eric OulashinEric Oulashinhttps://gitlab.synchro.net/main/sbbs/-/issues/585fixsbm can't fix message base2023-07-09T18:59:15ZNigel Reedfixsbm can't fix message base~~~
$ chksmb sysopstest/systesttest1
CHKSMB v3.20-Linux master/beca0e621 SMBLIB 3.00 - Check Synchronet Message Base
Checking sysopstest/systesttest1 Headers
0% #1 (000020) Current Watches, Warnings Header field contains control...~~~
$ chksmb sysopstest/systesttest1
CHKSMB v3.20-Linux master/beca0e621 SMBLIB 3.00 - Check Synchronet Message Base
Checking sysopstest/systesttest1 Headers
0% #1 (000020) Current Watches, Warnings Header field contains control characters
1% #2 (000320) Current Watches, Warnings Header field contains control characters
2% #3 (000620) Current Watches, Warnings Header field contains control characters
4% #4 (000920) Current Watches, Warnings Header field contains control characters
5% #5 (000C20) Current Watches, Warnings Header field contains control characters
7% #6 (000F20) Current Watches, Warnings Header field contains control characters
8% #7 (001220) Current Watches, Warnings Header field contains control characters
10% #8 (001520) Current Watches, Warnings Header field contains control characters
11% #9 (001820) Current Watches, Warnings Header field contains control characters
13% #10 (001B20) Current Watches, Warnings Header field contains control characters
14% #11 (001E20) Current Watches, Warnings Header field contains control characters
16% #12 (002120) Current Watches, Warnings Header field contains control characters
17% #13 (002420) Current Watches, Warnings Header field contains control characters
18% #14 (002720) Current Watches, Warnings Header field contains control characters
20% #15 (002A20) Current Watches, Warnings Header field contains control characters
21% #16 (002D20) Current Watches, Warnings Header field contains control characters
23% #17 (003020) Current Watches, Warnings Header field contains control characters
24% #18 (003320) Current Watches, Warnings Header field contains control characters
26% #19 (003620) Current Watches, Warnings Header field contains control characters
27% #20 (003920) Current Watches, Warnings Header field contains control characters
29% #21 (003C20) Current Watches, Warnings Header field contains control characters
30% #22 (003F20) Current Watches, Warnings Header field contains control characters
32% #23 (004220) Current Watches, Warnings Header field contains control characters
33% #24 (004520) Current Watches, Warnings Header field contains control characters
34% #25 (004820) Current Watches, Warnings Header field contains control characters
36% #26 (004B20) Current Watches, Warnings Header field contains control characters
37% #27 (004E20) Current Watches, Warnings Header field contains control characters
39% #28 (005120) Current Watches, Warnings Header field contains control characters
40% #29 (005420) Current Watches, Warnings Header field contains control characters
42% #30 (005720) Current Watches, Warnings Header field contains control characters
43% #31 (005A20) Current Watches, Warnings Header field contains control characters
45% #32 (005D20) Current Watches, Warnings Header field contains control characters
46% #33 (006020) Current Watches, Warnings Header field contains control characters
48% #34 (006320) Current Watches, Warnings Header field contains control characters
49% #35 (006620) Current Watches, Warnings Header field contains control characters
51% #36 (006920) Current Watches, Warnings Header field contains control characters
52% #37 (006C20) Current Watches, Warnings Header field contains control characters
53% #38 (006F20) Current Watches, Warnings Header field contains control characters
55% #39 (007220) Current Watches, Warnings Header field contains control characters
56% #40 (007520) Current Watches, Warnings Header field contains control characters
58% #41 (007820) Current Watches, Warnings Header field contains control characters
59% #42 (007B20) Current Watches, Warnings Header field contains control characters
61% #43 (007E20) Current Watches, Warnings Header field contains control characters
62% #44 (008120) Current Watches, Warnings Header field contains control characters
64% #45 (008420) Current Watches, Warnings Header field contains control characters
65% #46 (008720) Current Watches, Warnings Header field contains control characters
67% #47 (008A20) Current Watches, Warnings Header field contains control characters
68% #48 (008D20) Current Watches, Warnings Header field contains control characters
69% #49 (009020) Current Watches, Warnings Header field contains control characters
71% #50 (009320) Current Watches, Warnings Header field contains control characters
72% #51 (009620) Current Watches, Warnings Header field contains control characters
74% #52 (009920) Current Watches, Warnings Header field contains control characters
75% #53 (009C20) Current Watches, Warnings Header field contains control characters
77% #54 (009F20) Current Watches, Warnings Header field contains control characters
78% #55 (00A220) Current Watches, Warnings Header field contains control characters
80% #56 (00A520) Current Watches, Warnings Header field contains control characters
81% #57 (00A820) Current Watches, Warnings Header field contains control characters
83% #58 (00AB20) Current Watches, Warnings Header field contains control characters
84% #59 (00AE20) Current Watches, Warnings Header field contains control characters
85% #60 (00B120) Current Watches, Warnings Header field contains control characters
87% #61 (00B420) Current Watches, Warnings Header field contains control characters
88% #62 (00B720) Current Watches, Warnings Header field contains control characters
90% #63 (00BA20) Current Watches, Warnings Header field contains control characters
91% #64 (00BD20) Current Watches, Warnings Header field contains control characters
93% #65 (00C020) Current Watches, Warnings Header field contains control characters
94% #66 (00C320) Current Watches, Warnings Header field contains control characters
96% #67 (00C620) Current Watches, Warnings Header field contains control characters
97% #68 (00C920) Current Watches, Warnings Header field contains control characters
100%
Checking sysopstest/systesttest1 Data Blocks
100%
Checking sysopstest/systesttest1 Index
100%
Checking sysopstest/systesttest1 Hashes
100%
Status Total (=): 4
Total Indexes (=): 4
Active Indexes (=): 4
Active Headers (=): 4
Active Header Blocks ( ): 11 2,816 bytes used
Active Data Blocks ( ): 4 1,024 bytes used
Header Records ( ): 69
Deleted Indexes ( ): 0
Deleted Headers ( ): 65
Deleted Header Blocks ( ): 195 49,920 bytes used
Deleted Data Blocks ( ): 128 32,768 bytes used
Oldest Message (import) ( ): 160 days (0 max)
Largest Message (data) ( ): 390 bytes (#33)
Control Characters in Header Fields (!): 68
sysopstest/systesttest1 Message Base has Errors!
Total Deleted Messages : 65 82,688 bytes used
'fixsmb' can be used to repair many message base problems.
$ fixsmb sysopstest/systesttest1
FIXSMB v3.19-Linux master/beca0e621 SMBLIB 3.00 - Rebuild Synchronet Message Base
Opening sysopstest/systesttest1
0% #1 (000020) Current Watches, Warnings Not indexing deleted message
1% #2 (000320) Current Watches, Warnings Not indexing deleted message
2% #3 (000620) Current Watches, Warnings Not indexing deleted message
4% #4 (000920) Current Watches, Warnings Not indexing deleted message
5% #5 (000C20) Current Watches, Warnings Not indexing deleted message
7% #6 (000F20) Current Watches, Warnings Not indexing deleted message
8% #7 (001220) Current Watches, Warnings Not indexing deleted message
10% #8 (001520) Current Watches, Warnings Not indexing deleted message
11% #9 (001820) Current Watches, Warnings Not indexing deleted message
13% #10 (001B20) Current Watches, Warnings Not indexing deleted message
14% #11 (001E20) Current Watches, Warnings Not indexing deleted message
16% #12 (002120) Current Watches, Warnings Not indexing deleted message
17% #13 (002420) Current Watches, Warnings Not indexing deleted message
18% #14 (002720) Current Watches, Warnings Not indexing deleted message
20% #15 (002A20) Current Watches, Warnings Not indexing deleted message
21% #16 (002D20) Current Watches, Warnings Not indexing deleted message
23% #17 (003020) Current Watches, Warnings Not indexing deleted message
24% #18 (003320) Current Watches, Warnings Not indexing deleted message
26% #19 (003620) Current Watches, Warnings Not indexing deleted message
27% #20 (003920) Current Watches, Warnings Not indexing deleted message
29% #21 (003C20) Current Watches, Warnings Not indexing deleted message
30% #22 (003F20) Current Watches, Warnings Not indexing deleted message
32% #23 (004220) Current Watches, Warnings Not indexing deleted message
33% #24 (004520) Current Watches, Warnings Not indexing deleted message
34% #25 (004820) Current Watches, Warnings Not indexing deleted message
36% #26 (004B20) Current Watches, Warnings Not indexing deleted message
37% #27 (004E20) Current Watches, Warnings Not indexing deleted message
39% #28 (005120) Current Watches, Warnings Not indexing deleted message
40% #29 (005420) Current Watches, Warnings Not indexing deleted message
42% #30 (005720) Current Watches, Warnings Not indexing deleted message
43% #31 (005A20) Current Watches, Warnings Not indexing deleted message
45% #32 (005D20) Current Watches, Warnings Not indexing deleted message
46% #33 (006020) Current Watches, Warnings Not indexing deleted message
48% #34 (006320) Current Watches, Warnings Not indexing deleted message
49% #35 (006620) Current Watches, Warnings Not indexing deleted message
51% #36 (006920) Current Watches, Warnings Not indexing deleted message
52% #37 (006C20) Current Watches, Warnings Not indexing deleted message
53% #38 (006F20) Current Watches, Warnings Not indexing deleted message
55% #39 (007220) Current Watches, Warnings Not indexing deleted message
56% #40 (007520) Current Watches, Warnings Not indexing deleted message
58% #41 (007820) Current Watches, Warnings Not indexing deleted message
59% #42 (007B20) Current Watches, Warnings Not indexing deleted message
61% #43 (007E20) Current Watches, Warnings Not indexing deleted message
62% #44 (008120) Current Watches, Warnings Not indexing deleted message
64% #45 (008420) Current Watches, Warnings Not indexing deleted message
65% #46 (008720) Current Watches, Warnings Not indexing deleted message
67% #47 (008A20) Current Watches, Warnings Not indexing deleted message
68% #48 (008D20) Current Watches, Warnings Not indexing deleted message
69% #49 (009020) Current Watches, Warnings Not indexing deleted message
71% #50 (009320) Current Watches, Warnings Not indexing deleted message
72% #51 (009620) Current Watches, Warnings Not indexing deleted message
74% #52 (009920) Current Watches, Warnings Not indexing deleted message
75% #53 (009C20) Current Watches, Warnings Not indexing deleted message
77% #54 (009F20) Current Watches, Warnings Not indexing deleted message
78% #55 (00A220) Current Watches, Warnings Not indexing deleted message
80% #56 (00A520) Current Watches, Warnings Not indexing deleted message
81% #57 (00A820) Current Watches, Warnings Not indexing deleted message
83% #58 (00AB20) Current Watches, Warnings Not indexing deleted message
84% #59 (00AE20) Current Watches, Warnings Not indexing deleted message
85% #60 (00B120) Current Watches, Warnings Not indexing deleted message
87% #61 (00B420) Current Watches, Warnings Not indexing deleted message
88% #62 (00B720) Current Watches, Warnings Not indexing deleted message
90% #63 (00BA20) Current Watches, Warnings Not indexing deleted message
91% #64 (00BD20) Current Watches, Warnings Not indexing deleted message
93% #65 (00C020) Current Watches, Warnings Not indexing deleted message
100%
Sorting index...
Re-writing index...
Saving message base status (4 total messages).
Closing message base.
Done.
~~~
However running chksmb again shows the same issues. Let me know if you'd like me to upload any files to vert for you to investigate.https://gitlab.synchro.net/main/sbbs/-/issues/584IRC ip to decimal returning negative number2023-07-08T03:26:14ZNigel ReedIRC ip to decimal returning negative number[13:23] -eotlbbs.synchro.net- *** RemoteClient -- NICK craowiest ~blauvp@192.252.211.197 frugalbb.synchro.net -1057172539 :duening
192.252.211.197 should return 3237794757
[12:59] -eotlbbs.synchro.net- *** RemoteClient -- NICK cruukest...[13:23] -eotlbbs.synchro.net- *** RemoteClient -- NICK craowiest ~blauvp@192.252.211.197 frugalbb.synchro.net -1057172539 :duening
192.252.211.197 should return 3237794757
[12:59] -eotlbbs.synchro.net- *** RemoteClient -- NICK cruukest ~greawinge@199.229.254.129 frugalbb.synchro.net -941228415 :truuped
199.229.254.129 should return 3353738881https://gitlab.synchro.net/main/sbbs/-/issues/583IRC IPs sometimes sent a in x.x.x.x format not decimal IPs2023-07-08T03:37:06ZNigel ReedIRC IPs sometimes sent a in x.x.x.x format not decimal IPs<code>
[02:35] -eotlbbs.synchro.net- *** Client -- Client connecting: mrnelgin (nelgin@47.186.47.220) [47.186.47.220] {10}
[02:35] -eotlbbs.synchro.net- *** Global -- from services.synchro.net: WARNING: invalid IP address `47.186.47.220'...<code>
[02:35] -eotlbbs.synchro.net- *** Client -- Client connecting: mrnelgin (nelgin@47.186.47.220) [47.186.47.220] {10}
[02:35] -eotlbbs.synchro.net- *** Global -- from services.synchro.net: WARNING: invalid IP address `47.186.47.220' for new nick mrnelgin
</code>
I first noticed this while investigating another issue:
This is correct:
<code>
[15:16] -eotlbbs.synchro.net- *** RemoteClient -- NICK deubiest ~kuofinger@51.68.79.223 reality.synchro.net 860114911 :paerl
[15:16] -eotlbbs.synchro.net- *** RemoteClient -- NICK pluamly ~greiwt@tor-exit-63.for-privacy.net reality.synchro.net 3118228799 :braukest
</code>
This is not:
<code>
[13:30] -eotlbbs.synchro.net- *** RemoteClient -- NICK luca50__ ~andchat54@host-87-0-152-9.retail.telecomitalia.it veleno.synchro.net 87.0.152.9 :AndChat542100
[13:30] -eotlbbs.synchro.net- *** Global -- from services.synchro.net: WARNING: invalid IP address `87.0.152.9' for new nick luca50__
[13:34] -eotlbbs.synchro.net- *** RemoteClient -- NICK LinksGetter ~irclib@vert.synchro.net vert.synchro.net 71.95.196.34 :irclib.js-1.24
[13:34] -eotlbbs.synchro.net- *** Global -- from services.synchro.net: WARNING: invalid IP address `71.95.196.34' for new nick LinksGetter
</code>
Server<>Server code needs to be audited to make sure decimal IP addresses are passed when expected.https://gitlab.synchro.net/main/sbbs/-/issues/581IRC - add reputation block list (RBL) capability to synchronet irc2023-07-08T03:37:45ZKeyop TroyIRC - add reputation block list (RBL) capability to synchronet ircRecently we have had spam bots hammmer the various irc channels on the Synchronet irc service (irc.synchro.net).
Analysis of the source IP's of the bots show that in the most recent attack there was a perfect match for the IRC RBL known...Recently we have had spam bots hammmer the various irc channels on the Synchronet irc service (irc.synchro.net).
Analysis of the source IP's of the bots show that in the most recent attack there was a perfect match for the IRC RBL known as dronebl (dronebl.org). See below for examples.
This request is to add the capability to utilise RBL service(s) including but not limited to drobebl to irc to help Synchronet sysop's combat the threat of their irc service being attacked by such bots.
It would be useful to include dronebl as the default RBL and allow the sysop to add additional ones as required.
----------
Query:
152.180.149.193.dnsbl.dronebl.org
A Record:
127.0.0.3
TTL:
300
DB_rc:
IRC Drone
TXT:
IRC spam drone (litmus/sdbot/fyle)
----------
72.155.205.67.dnsbl.dronebl.org
A Record:
127.0.0.3
TTL:
300
DB_rc:
IRC Drone
TXT:
IRC spam drone (litmus/sdbot/fyle)
----------https://gitlab.synchro.net/main/sbbs/-/issues/580IRC - servers need to support RAKILL to remove akills2023-07-08T03:38:06ZNigel ReedIRC - servers need to support RAKILL to remove akillsJul 4 21:39:36 bbs ircd[691]: [RAW->nelgin]: :eotlbbs.synchro.net NOTICE nelgin :*** Notice -- Server services.synchro.net sent unrecognized command: RAKILL 24.18.7.241 *
Servers need to support RAKILL to remove akill lines. WIthout it...Jul 4 21:39:36 bbs ircd[691]: [RAW->nelgin]: :eotlbbs.synchro.net NOTICE nelgin :*** Notice -- Server services.synchro.net sent unrecognized command: RAKILL 24.18.7.241 *
Servers need to support RAKILL to remove akill lines. WIthout it, each irc admin would have to manually remove the akill line as displayed in /stats khttps://gitlab.synchro.net/main/sbbs/-/issues/579IRC channels with 0 users in /list2023-10-24T01:00:50ZNigel ReedIRC channels with 0 users in /listAs noted by keyop, when using /list there are a large number of channels that exist with 0 users. This shouldn't happen. A channel should disappear once there are 0 users.
![image](/uploads/a8e00b132d827330deed9f9b9f0ffc65/image.png)As noted by keyop, when using /list there are a large number of channels that exist with 0 users. This shouldn't happen. A channel should disappear once there are 0 users.
![image](/uploads/a8e00b132d827330deed9f9b9f0ffc65/image.png)