open https://gitlab.synchro.net/main/sbbs/-/issues/652

We have a number of servers running versions of ircd less than 1.10. They're not supporting the new dronebl lookup which, in turn, opens our network to flooding. Also, many of these older servers contain bugs that may affect the network and/or are misconfigured (there's one that doesn't have a U:line for services so I may have to jupiter that until it's fixed).

I would suggest that, with help from @rswindell with an increase in version, vert could update to the latest version and cvs could stay at the current version for a couple of weeks to allow sysops to upgrade so we don't lose the entire network.

Or, we can permit clients to operate behind one level as long as they are at 1.10 or above. There's a few options, but we really need to get everyone on 1.10.

Finally, I've tried contacting sysops directly through their BBS but it seems like some of them are slow to respond, or just don't care.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/652#note_4270

Closing this with the technical basis that a hub (or a dummy server running a JS script) should be doing the RBL checking and sending a KILL downstream. We can't trust that any leaf is doing a check properly, so we'll assert it ourselves.

I'll work with nelgin next week on this.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/652
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: forbid out of date irc servers joining the network
By: Nigel Reed to GitLab issue in main/sbbs on Fri Sep 29 2023 01:31:37

open https://gitlab.synchro.net/main/sbbs/-/issues/652
We have a number of servers running versions of ircd less than 1.10. They're not supporting the new dronebl lookup which, in turn, opens our network to flooding. Also, many of these older servers contain
bugs that may affect the network and/or are misconfigured (there's one that doesn't have a U:line for services so I may have to jupiter that until it's fixed).

<CUT>

Or, we can permit clients to operate behind one level as long as they are at 1.10 or above. There's a few options, but we really need to get everyone on 1.10.

I would agree with this latter case. for example in my case, i work out of town a ton lately on major airport projects so that means i'm not able to admin as much although do try and log in at least on a daily basis to telnet for mail etc.

I wonder if it's feasible that the ZC/NC "should" have an email address for the nodes, so that may also be an option

charlie

---
þ Synchronet þ My Brand-New BBS
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)