From owner-cvs-all Mon Oct 9 14: 9:21 2000 Delivered-To: cvs-all@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 5D1C637B66D; Mon, 9 Oct 2000 14:09:17 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e99L8nX03616; Mon, 9 Oct 2000 14:08:49 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Matt Dillon Cc: Warner Losh , Jeroen Ruigrok van der Werven , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc inetd.conf In-Reply-To: Message from Matt Dillon of "Mon, 09 Oct 2000 00:55:54 PDT." <200010090755.e997tsb02934@earth.backplane.com> Date: Mon, 09 Oct 2000 14:08:49 -0700 Message-ID: <3612.971125729@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to imagine someone setting up a bunch of UNIX > boxes in a rack using a windows laptop rather then a unix laptop... Happens all the time. Like I said, most of the good diagnostic software runs under Windows. > and failing. Normally I assume that my network is insecure, even Again, if the systems are talking only to eachother and there's no outside link on the hub then they're as secure as they need to be until such time as you bring them into service. I've seen such scenarios frequently in the field. > And also, in order to make telnet operate out of the box you have > to setup a password anyway. That's part of FreeBSD's standard install. I honestly don't see anything in your email which refutes my essential point at all. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message