From owner-freebsd-hackers Sat Jun 28 01:01:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA10819 for hackers-outgoing; Sat, 28 Jun 1997 01:01:15 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA10813 for ; Sat, 28 Jun 1997 01:01:10 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id BAA02776; Sat, 28 Jun 1997 01:00:14 -0700 (PDT) To: Simon Shapiro cc: Bruce Evans , mburgett@cmnsens.zoom.com, freebsd-hackers@FreeBSD.ORG Subject: Re: com console, and h/w flow control... In-reply-to: Your message of "Sat, 28 Jun 1997 00:14:56 PDT." Date: Sat, 28 Jun 1997 01:00:14 -0700 Message-ID: <2772.867484814@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Actually, we are building just such system right now. We ridicule > Slowlaris to no end for their incredible stupidity by having just such a > ``feature''. > > I am SURE I am missing something in this discussion... A good grasp of terminal server security? :-) Seriously, I have to wonder at this whole line of inquiry. Let's forget FreeBSD for a moment and say that I've got the console ports to all my cisco routers wired up to such a terminal server. Can you seriously tell me that I'd be in my right mind to let _anyone_ other than the admin staff be able to log into this particular terminal server, much less know the phone numbers for it? There's a lot you can do if you've got a wired-in connection to the serial console of any ten devices I can name, much less FreeBSD, and you guard that connectivity just as jealously as you guard the physical security of the machine or you expect your life to suck. Jordan