home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!usenet.ins.cwru.edu!skybridge!wb8foz
- From: wb8foz@skybridge.SCL.CWRU.Edu (David Lesher)
- Newsgroups: alt.security
- Subject: Re: Detecting an Ethernet Tap
- Date: 11 Nov 1992 01:06:47 GMT
- Organization: NRK Clinic for habitual NetNews abusers - Beltway Annex
- Lines: 20
- Message-ID: <1dpmb7INNt2f@usenet.INS.CWRU.Edu>
- References: <12914@hq.hq.af.mil> <GUENTHER.92Nov9175156@amcl5.stolaf.edu> <1992Nov10.031126.14041@magnus.acs.ohio-state.edu>
- Reply-To: wb8foz@skybridge.scl.cwru.edu (David Lesher)
- NNTP-Posting-Host: skybridge.scl.cwru.edu
-
- This is basically impossible.
- If your tapper has any brains at all, {s}he will use a hi-z tap
- that even a TDR will miss midst the returns from small cable
- kinks, bends etc.
-
- Your options:
- 1) encrypt all traffic
- 2) protect the etherhose
- a) Post guards every 25 metres [don't laugh...]
- b) run fiber inside inner rigid conduit. Run it inside
- larger one. Fill space between with neurotoxins under
- pressure......
-
-
-
- --
- A host is a host from coast to coast..wb8foz@skybridge.scl.cwru.edu
- & no one will talk to a host that's close..........................
- Unless the host (that isn't close).........................pob 1433
- is busy, hung or dead....................................20915-1433
-