Subj : How to handle the port 23 script kiddies
To   : All
From : Bj”rn Felten
Date : Wed Mar 14 2018 00:41:13

I really do want to keep my port 23 open, so that my users can telnet to my 
BBS.

   But as most of you probably know, there's a huge operation going on with 
hijacked computers trying to connect to other port 23 computers.

   Well, if you like me have Argus setup to answer incoming port 23 calls, you 
probably know that there's very little double escape character response. So how 
do you handle this?

   In the Doors setup the only nonprintable character available is the escape 
character (a backslash). If character/return had something like that it would 
be much easier. But here's how I've done it:

   http://felten.se/ny.jpg

   Originally I was planning on sending a huge response (as in typing a big 
exe-file) but I abandoned that idea since it meant that my system was hanging 
after the remote system quickly disconnected.

   But the 'type' command does not compute (you need 'cmd type' to make it 
work), so the connection swiftly is disconnected.

   As always: RFC...  8-)

...

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
 * Origin: news://eljaco.se (2:203/2)

.