From owner-freebsd-security Fri Jul 31 13:11:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16505 for freebsd-security-outgoing; Fri, 31 Jul 1998 13:11:48 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16500 for ; Fri, 31 Jul 1998 13:11:46 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.8) id OAA05278; Fri, 31 Jul 1998 14:11:04 -0600 (MDT) Message-Id: <199807312011.OAA05278@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 31 Jul 1998 14:06:28 -0600 To: sthaug@nethelp.no, reidar@ravn.no From: Brett Glass Subject: Re: Where are your logs? Methods of logging? Cc: security@FreeBSD.ORG In-Reply-To: <7823.901899430@verdi.nethelp.no> References: <3.0.32.19980731162500.00869ce0@trost.ravn.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It was probably a TP RS-232 cable. --Brett At 05:37 PM 7/31/98 +0200, sthaug@nethelp.no wrote: >> I haven't done it myself, but I've heard that some cut (!) the >> "send"-wires on the TP-cable to the secure machine -- making it >> impossible to reach it via the network. > >Sorry, doesn't work with TP, since TP depends on "link pulses" to detect >that the link is up. A similar arrangement using AUI & coax was described >by Bellovin & co quite a while, though. > >Steinar Haug, Nethelp consulting, sthaug@nethelp.no > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message