From owner-freebsd-security Fri Mar 26 14:59:37 1999 Delivered-To: freebsd-security@freebsd.org Received: from quaggy.ursine.com (lambda.blueneptune.com [209.133.45.179]) by hub.freebsd.org (Postfix) with ESMTP id B73A714C58 for ; Fri, 26 Mar 1999 14:59:35 -0800 (PST) (envelope-from fbsd-security@ursine.com) Received: from michael (lambda.ursine.com [209.133.45.69]) by quaggy.ursine.com (8.9.2/8.9.2) with ESMTP id OAA17715 for ; Fri, 26 Mar 1999 14:59:17 -0800 (PST) (envelope-from fbsd-security@ursine.com) Message-ID: <199903261459220480.423A1371@quaggy.ursine.com> In-Reply-To: <199903261618.EAA16015@aniwa.sky> References: <199903261618.EAA16015@aniwa.sky> X-Mailer: Calypso Evaluation Version 3.00.00.13 (2) Date: Fri, 26 Mar 1999 14:59:22 -0800 From: "Michael Bryan" To: freebsd-security@freebsd.org Subject: Re: xinetd vs. tcp_wrappers Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 3/27/99 at 4:18 AM Andrew McNaughton wrote: >marker@trolldom.oss.uswest.net said: >> I have, however, been unable to get xinetd to >> >> 1) send me mail when someone touches my machines in a >> way i've not said is ok, > >Supposing someone is sniffing your network, and you are >reading your mail from another machine, does this mail >give away any otherwise unknown information about the >configuration of the machine? Why would you be doing an admin task over the network in the clear in the first place? My personal opinion is that every admin task should either be done on the console, or via a secure/encrypted communication channel, if at all possible. Michael Bryan fbsd-security@ursine.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message