Main issueshttps://gitlab.synchro.net/groups/main/-/issues2023-08-15T02:05:23Zhttps://gitlab.synchro.net/main/sbbs/-/issues/598mqtt: output topic not conducive to nodered/html output2023-08-15T02:05:23ZNigel Reedmqtt: output topic not conducive to nodered/html outputWhen using the output topic to spy on a node, it's not very readable due to ansi graphics codes and characters.
![image](/uploads/59e438e19ef75a0f577677d18f708131/image.png)
I can only think of pre-formatting the output by either
1: Re...When using the output topic to spy on a node, it's not very readable due to ansi graphics codes and characters.
![image](/uploads/59e438e19ef75a0f577677d18f708131/image.png)
I can only think of pre-formatting the output by either
1: Removing all escape codes, including color and graphics so it's readable
2: Convert colors and graphics, as much as possible, to html
It could be possible to change output to have something like
sbbs/+/node/+/output/raw (as it comes)
sbbs/+/node/+/output/html (preformatted html)
sbbs/+/node/+/output/stripped (plain old text with no color/graphics)
This would allow different users to pick whatever format works for them.
I considered the amount of data and it's not really a lot unless you've got 10 users bombarding each other!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/596war crashes when game.save.json is 0 bytes2023-07-26T21:00:02ZNigel Reedwar crashes when game.save.json is 0 bytesWhen trying to run war or warupd, it'll cash with an error in line 135 of warcommon.js
As a workaround, change into the worlds directory and then look in each subdir for a 0 length game.save.json file and delete it. Run the game again a...When trying to run war or warupd, it'll cash with an error in line 135 of warcommon.js
As a workaround, change into the worlds directory and then look in each subdir for a 0 length game.save.json file and delete it. Run the game again and it should work.
Documenting this both as a fix and a workaround.DeucеDeucеhttps://gitlab.synchro.net/main/sbbs/-/issues/595Need workaround for possible broken tera term zmodem implimentation2023-07-26T07:05:50ZNigel ReedNeed workaround for possible broken tera term zmodem implimentationI tried to receive a file from my BBS using both ssh and telnet and received the same issue. Keyop also had a user with the same issue of hanging zmodem but wasn't able to determine the client:
~~~
Jul 26 01:56:41 bbs synchronet: term N...I tried to receive a file from my BBS using both ssh and telnet and received the same issue. Keyop also had a user with the same issue of hanging zmodem but wasn't able to determine the client:
~~~
Jul 26 01:56:41 bbs synchronet: term Node 1 <Nelgin> Executing external: /sbbs/exec/sexyz 129 -raw sz /sbbs/data/dirs/metronet/metronetmetronet/METLIST.Z21
Jul 26 01:56:41 bbs synchronet: term Node 1 <Nelgin> sexyz: Synchronet External X/Y/ZMODEM v3.0 master/f9a44f56e Copyright Rob Swindell
Jul 26 01:56:51 bbs synchronet: term Node 1 <Nelgin> sexyz: !Receive timeout (10 seconds)
Jul 26 01:56:51 bbs synchronet: term Node 1 <Nelgin> sexyz: !zmodem_send_file UNEXPECTED TIMEOUT received instead of ZRINIT
Jul 26 01:56:52 bbs synchronet: term Node 1 <Nelgin> sexyz: !zmodem_recv_hex_header HEX header not terminated with LF: 141 (8Dh)
Jul 26 01:56:52 bbs synchronet: term Node 1 <Nelgin> sexyz: !zmodem_recv_header detected an INVALID HEADER
~~~
in one case this apparently caused my user's connection to hang and didn't disconnect him when he dropped. He was told he was already logged in when attempting to login again.
All works fine with SyncTerm.Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/594Feature Request - Add support for virtual ftp users and directories2023-07-19T00:12:07ZNigel ReedFeature Request - Add support for virtual ftp users and directoriesI would like to add users that can access their own directory space without having to create a BBS users.
I would create directories such as /sbbs/ftp/fred /sbbs/ftp/tom /sbbs/ftp/ethel
Then store their details in a .ini file
[fred]
d...I would like to add users that can access their own directory space without having to create a BBS users.
I would create directories such as /sbbs/ftp/fred /sbbs/ftp/tom /sbbs/ftp/ethel
Then store their details in a .ini file
[fred]
dir=/sbbs/ftp/fred
pw=fredspw
perms=pgdlco
p=put
g=get
d=delete
l=list directory
c=allowed to use cd
o = allow overwrite of existing files
The use of a .ini file would make changing passwords easier.Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/593Feature Request - Add feature within SCFG to change Forward E-mail to NetMail...2023-07-15T22:13:06ZKeyop TroyFeature Request - Add feature within SCFG to change Forward E-mail to NetMail operation to allow sending to both local and internet email accountsPresently when selecting Forward E-mail to NetMail, there are two modes of operation.
1 - Send emails to the local BBS account ONLY
2 - Send emails to the user's internet email account ONLY
This feature request is to allow a third opti...Presently when selecting Forward E-mail to NetMail, there are two modes of operation.
1 - Send emails to the local BBS account ONLY
2 - Send emails to the user's internet email account ONLY
This feature request is to allow a third option of
3 - Send emails to both the local BBS account AND the user's internet email account
This could be achieved for example by:
Changing the SCFG-Message Options->Allow Forwarding to NetMail" from a toggle "Yes/No" to "Yes/No/Both".Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/592Feature Request - Option to hide "[M] Forward E-mail to NetMail" in user sett...2023-09-11T16:13:24ZKeyop TroyFeature Request - Option to hide "[M] Forward E-mail to NetMail" in user settingsAdd toggle option in SCFG to hide "[M] Forward E-mail to NetMail" within user settings when a user attempts to edit their own settings.
This will allow the sysop to decide which users are able to use this feature or not.
This toggle sh...Add toggle option in SCFG to hide "[M] Forward E-mail to NetMail" within user settings when a user attempts to edit their own settings.
This will allow the sysop to decide which users are able to use this feature or not.
This toggle should not affect the local useredit (exec/uedit) or ;UEDIT capabilities (used by the sysop).Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/591Feature Request - New user prompts, add "Should user be asked if local emails...2023-07-15T21:58:11ZKeyop TroyFeature Request - New user prompts, add "Should user be asked if local emails should be forwarded to netmails? Y/N"If SCFG->Message Options->Allow Forwarding to NetMail is enabled, then new users would be asked if they wanted this feature enabled or disabled during registration.
This request is to allow the Sysop to remove (or not as is now) this qu...If SCFG->Message Options->Allow Forwarding to NetMail is enabled, then new users would be asked if they wanted this feature enabled or disabled during registration.
This request is to allow the Sysop to remove (or not as is now) this question during new user registration.
Default (yes) should be set to retain current look & feel with option to select "No" in SCFG if required.Rob 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/588SCFG in X11 mode defaults to tiny font/size on 4K monitor2023-07-30T11:22:31ZRob SwindellSCFG in X11 mode defaults to tiny font/size on 4K monitorSee https://web.synchro.net/scfg%20small.png for exampleSee https://web.synchro.net/scfg%20small.png for exampleRob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/58764-bit Windows builds2023-08-25T22:08:26ZRob Swindell64-bit Windows buildsIt seems to be the time to start looking into building 64-bit (x64) executables for Windows.
- sbbsctrl (built with C++Builder 6) definitely won't be moving to 64-bit as is
- 3rd party libs (libmozjs, cryptlib, sdl) might provide their ...It seems to be the time to start looking into building 64-bit (x64) executables for Windows.
- sbbsctrl (built with C++Builder 6) definitely won't be moving to 64-bit as is
- 3rd party libs (libmozjs, cryptlib, sdl) might provide their own challenges
But the additional Windows security and address space available to 64-bit Windows programs might be important to some sysops, if not now, in the not too distant future.Rob SwindellRob Swindellhttps://gitlab.synchro.net/main/sbbs/-/issues/586sprintf_s2023-07-09T21:57:32ZRob Swindellsprintf_sConsider a build option to use sprintf_s (C standard, but optional) instead of snprintf/safe_snprintf for build environments that support it.Consider a build option to use sprintf_s (C standard, but optional) instead of snprintf/safe_snprintf for build environments that support it.https://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/582Named security levels2023-07-06T20:08:29ZRob SwindellNamed security levelsSimilar to how web-boards sometimes display a "title" along with a user's name (e.g. "admin", "new user", etc.), we could display a short description (e.g. in message headers, user profile viewers) that correlates with a user's security ...Similar to how web-boards sometimes display a "title" along with a user's name (e.g. "admin", "new user", etc.), we could display a short description (e.g. in message headers, user profile viewers) that correlates with a user's security level. e.g. in main.ini
```
[level:0]
desc=Nobody
[level:50]
desc=New user
[level:51]
desc=Validated user
[level:90]
desc=Co-Sysop
[level:99]
desc=Sysop
```
Fill-in/duplicate descriptions for ranges of levels?Rob SwindellRob Swindellhttps://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)