Subj : Bots Be Gone
To   : Shurato
From : opicron
Date : Wed Apr 16 2025 12:42:14

 Sh>  op> Al> Are you tired of bots trying to log onto your Mystic BBS?
 Sh>  op> Al> Tired of "hackers" who just slap a bunch of random keys instead
 Sh>  op> Al> of logging in?
 Sh>  op> Very much ^^, wrote a bunch of scripts which fired to check for stale
 Sh>  op> connections.

 Sh> Not using mystic, but by locking out all non-ANSI connections, all of the
 Sh> bots are stopped.  I simply have my ascii logon screen display "CP437
 Sh> connection required" then the macro to disconnect.  I don't have any ASCII
 Sh> support any way; I never created a non-ansi menu system.  A little elite o
 Sh> me, but most users even on older systems have ANSI terms.

Yeah, I did that with mystic too. But when I call my scripts on the shell by invoking them in Mystic they also run as non-ansi.
Of course there is a way around that, but I dont feel like making an background process act as they are full term type. 

So, to make sure my custom scripts run from shell I had to undo dropping non-ansi. 

My second attempt was to force ANSI calls only, but then the term type doesnt get detected. If Mystic does not detect term type it does not pick up the resolution (80x25 or 132x37) of the call terminal. 

As daForze is most pretty on 132x37 it solided the fact to detect termtype, and to allow non-ansi for custom shell scripts.

oP!

.... We'll get along fine as soon as you realize that I'm God!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: TheForze - bbs.theforze.eu:23 (21:3/126)

.