Are you tired of bots trying to log onto your Mystic BBS?
Tired of "hackers" who just slap a bunch of random keys
instead of logging in?

I forget how I did this because I set it up a long time ago,
but when someone calls my board, the first thing they see is
a menu like this:

"Hello, welcome to Bunker 3. If you are a human being,
press the number 1 on your keyboard."

It really slows people down. After a person finally
realizes that they must poke the 1 key, they are presented
with the actual login screen.

... Read messages, not taglines

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: From the depths of Bunker 3 (21:1/130)

Are you tired of bots trying to log onto your Mystic BBS?
Tired of "hackers" who just slap a bunch of random keys
instead of logging in?

Very much ^^, wrote a bunch of scripts which fired to check for stale connections.

In the end I went with a stricter version of my custom Mystic login matrix rainfall mod, it times out after 10 seconds, except when a key is pressed. It adds a few seconds more. Total timeout is about 30 seconds, works like a charm.

Check it out on daForze :) -shameless self plug- ooopz.

It really slows people down. After a person finally
realizes that they must poke the 1 key, they are presented
with the actual login screen.

Very true, nice solution also.

oP!

... Pizza: Nature's perfect food.

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

Are you tired of bots trying to log onto your Mystic BBS?
Tired of "hackers" who just slap a bunch of random keys instead
of logging in?

Very much ^^, wrote a bunch of scripts which fired to check for stale connections.

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

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,999) (ssh login 'bbs' password 'shsbbs')


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (21:2/148)

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

This works well, yeah.

That said, I guess it depends on the implementation, but I found ANSI detection wasn't foolproof once you're a little off the beaten track.

Obscure example, but I had Novaterm (C64) and DC_Telnet (Amiga) both fail the ANSI detection in either Net2BBS or Ezycom in my setup (I don't remember exactly which).

That said, if it stops all the bots, and only negatively affects a couple of clients, then it's probably worthwhile.

Cheers

--- Ezycom V2.15g0 01FD0295
* Origin: >> Pool's Open - The RetroSwim BBS (21:2/121)

Are you tired of bots trying to log onto your Mystic BBS?
Tired of "hackers" who just slap a bunch of random keys instead of logging in?

Very much ^^, wrote a bunch of scripts which fired to check for stale connections.

Not using mystic, but by locking out all non-ANSI connections, all of the bots are stopped. I simply have my ascii logon screen display "CP437 connection required" then the macro to disconnect. I don't have any ASCII support any way; I never created a non-ansi menu system. A little elite o 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)

BY: Alonzo (21:1/130)

|11A|09> |10Are you tired of bots trying to log onto your Mystic BBS?|07 |11A|09> |10Tired of "hackers" who just slap a bunch of random keys|07
|11A|09> |10instead of logging in?|07
Would a mailer mode reduce most of those people?


--- WWIV 5.9.03748[Windows]
* Origin: inland utopia * california * iutopia.duckdns.org:2023 (21:4/108)

* In a message originally to Shurato, Retroswim said:

Not using mystic, but by locking out all non-ANSI connections, all of

the

bots are stopped. I simply have my ascii logon screen display "CP437 connection required" then the macro to disconnect. I don't have any

ASCII

support any way; I never created a non-ansi menu system. A little

elite of

me, but most users even on older systems have ANSI terms.

This works well, yeah.

That said, I guess it depends on the implementation, but I found ANSI detection wasn't foolproof once you're a little off the beaten track.

Obscure example, but I had Novaterm (C64) and DC_Telnet (Amiga) both fail the ANSI detection in either Net2BBS or Ezycom in my setup (I don't
remember exactly which).

That said, if it stops all the bots, and only negatively affects a couple
of clients, then it's probably worthwhile.

I had a DCT user that this worked with, haven't had any NovaTerm users.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,999) (ssh login 'bbs' password 'shsbbs')


---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (21:2/148)