home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   BBS_CARNIVAL      Your BBS software rules and others suck      5,461 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 5,021 of 5,461   
   Rob Swindell to Dennis Scott   
   BBS Software Timeout Values   
   06 Apr 23 17:01:10   
   
   TZUTC: -0700   
   MSGID: 11168.bbs_carn@1:103/705 2894bee6   
   REPLY: 11167.bbs_carn@1:103/705 2894ab4f   
   PID: Synchronet 3.20a-Linux master/fcf4a0012 Apr  4 2023 GCC 12.2.0   
   TID: SBBSecho 3.20-Linux master/f4dcbf61d Apr  5 2023 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.104   
     Re: BBS Software Timeout Values   
     By: Dennis Scott to Rob Swindell on Thu Apr 06 2023 03:37 pm   
      
    >   Re: BBS Software Timeout Values   
    >   By: Rob Swindell to Dennis Scott on Tue Apr 04 2023 09:56 am   
    >   
    >  > to very simple "denial of service" attacks by users either accidentally   
    >  > or purposefully just "walking away from the keyboard" once connected and   
    >  > tying up all their nodes.   
    >   
    > DOS attacks are a real threat but that really should be handled on the front   
    > end of the BBS or at the firewall, I would hope anyhow.   
      
   I was referring to a different kind of DOS "attack". If the sysop wants to   
   suppoort n-users connecting, authenticating, and then walking away from their   
   keyboards, that sysop would need n-nodes on the BBS. Luckily a node is just   
   another and some config files these days (not an additional phone line or   
   computer), but still, it's a *finite* resource.   
      
    > When are you coming out with your 100 node version Rob?   
      
   Current versions of Synchronet support up to 250 nodes. Realistically, nobody   
   configures anywhere near that many nodes mainly because configuring door games   
   to support dozens of nodes (for many multinode doors, anyway), is a big   
   hassle. It's much easier to just enforce a maximum duration of user inactivity   
   and keep the number of configured nodes to some a number you'd reasonably   
   expect to need for *active* user connections.   
   --    
                                               digital man (rob)   
      
   Breaking Bad quote #8:   
   I want Shania Twain to give me a tuggy. Guess what? That ain't happening either   
   Norco, CA WX: 72.3øF, 22.0% humidity, 14 mph ESE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.20-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 1/123 10/0 1 15/0 18/200 90/1 102/401 103/1 705 105/81 106/201   
   SEEN-BY: 123/131 129/305 153/7715 214/22 218/0 1 215 501 700 720 810   
   SEEN-BY: 218/820 840 850 860 880 226/30 227/114 229/110 111 112 113   
   SEEN-BY: 229/206 275 307 317 400 424 426 428 452 470 550 664 700 266/512   
   SEEN-BY: 280/464 282/1038 301/1 317/3 320/219 322/757 342/200 396/45   
   SEEN-BY: 460/58 633/280 712/848   
   PATH: 103/705 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca