Subj : Automatically blocking co
To : fluid
From : Digital Man
Date : Wed Jun 05 2024 01:53 pm
Re: Automatically blocking co
By: fluid to Dumas Walker on Wed Jun 05 2024 03:34 pm
> Re: Automatically blocking co
> By: Dumas Walker to DIGITAL MAN on Tue Jun 04 2024 09:34 am
>
> > I ran into issues (with 3.19 and before, anyway) where people or bots
> > were hitting the telnet port rapidly and apparently not trying to log in,
> > which meant they were not being throttled.
>
> > It would eventually "crash" telnet. I would have expected it to take
> > down the whole terminal server but SSH would still be working. I would
> > only
> > find out about it when a user complained that the BBS was down. A
> > recycle of sbbs would fix it.
>
> I did not have this issue specifically, but I had an issue where running
> telnet on port 23 led to me being unable to connect to my own system while
> no real users were connected multiple times over the past 3 days.
>
> My solution was the old-school "press escape twice to enter the system"
> prompt that times out in 15 seconds.
I think the better solution is to use ANSI terminal detection. This is how the login.js auto-reduces the inactivity timeout for bots (which don't support ANSI). It's better to make everything these things transparent to users.
--
digital man (rob)
Steven Wright quote #16:
When everything is coming your way, you're in the wrong lane.
Norco, CA WX: 81.3�F, 55.0% humidity, 13 mph W wind, 0.00 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net
