TZUTC: -0500   
   MSGID: 612.hobbynt-hnetsyso@954:895/7 28f2d6f2   
   REPLY: 954:895/45 ad39897d   
   PID: Synchronet 3.20a-Win32 master/777fb6d8b Jun 13 2023 MSC 1929   
   TID: SBBSecho 3.20-Win32 master/777fb6d8b Jun 13 2023 MSC 1929   
   BBSID: TBOLT   
   CHRS: ASCII 1   
    Tim,   
       
    Si> Yeah I've been blocked again .. I think it has to do with all the   
    Si> HACKER attempts .. my Server Provider is in Louisiana .. and my proxy   
    Si> provider was Canada, but I updated to Chicago. It was working .. then   
    Si> this morning, it stopped .. so I've put it back to 2323   
      
      I have a CAPTCHA deal set up (Thanks to Lord Blackfair, one of the    
    Synchronet Sysops). He did a second version that automatically changed   
    the random code with each logon or incorrect attempt...but I lost that    
    one in a crash, so I went back to the original one.   
        
      I figured how to decompile the source code, and created one with a    
    new random code (that I got from a random number utility for Windows),   
    then recompiled it, and created 288 separate files, with accompanying   
    batch files. These combined with the Windows 10 Task Scheduler, change    
    the code every 5 minutes around the clock. The bots never see this, and    
    so they're "stuck" there until they disconnect. Plus, if I see from the    
    log that a certain IP address is "slamming the port", I put it into the    
    IP trashcan file, and they are permanently blocked from conneting again.    
        
      If these bots were to somehow enter the right code (highly unlikely),   
    if they entered something like "admin", "root", "Sysop", etc., they get   
    disconnected. The same applies for an FTP connect...Synchronet puts a    
    "temporary ban" on the IP, and once I notice that, it becomes permanent.    
       
      What users do outside the BBS is their business, but they're a guest    
    in my residence at logon...and it has been that way since the BBS first    
    went online nearly 33 years ago now.   
       
      While my telnet port is the traditional one, I had to change the SSH   
     and QOTD (Quote Of The Day) ports to a non-conventional value, as they    
     were getting slammed by the bots. I do have a door on the BBS related    
     doors menu for verified users in good standing, with the needed port    
     info. If those start getting slammed, I'll just change the values, and    
     update the door info.    
        
       It's a shame that Sysops have had to worry about twits all these years.   
        
     Daryl   
        
   ... Dachshund Raincoat - When you need to keep your weiner from getting wet.   
   === MultiMail/Win v0.52   
   --- SBBSecho 3.20-Win32   
    * Origin: The Thunderbolt BBS - Little Rock, Arkansas (954:895/7)   
   SEEN-BY: 229/110 426 470 700 291/111 5075/35   
   PATH: 229/470 426