full-disclosure - Caching a sniffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ONECINPABBOKJMJLEHOCAEBLELAA.jbaldini@newmassmedia.com>
From: jbaldini at newmassmedia.com (Justin Baldini)
Subject: Caching a sniffer

It would probably be better to build it at the switch level.  I would think
there would be a change in resistance when there is ANYTHING added/removed
from the cabling that could be measured by the switch.  You could then have
it disable that segment upon such detection if you'd like.

-jb

-----Original Message-----
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com]On Behalf Of Simon
Richter
Sent: Friday, March 12, 2004 7:31 AM
To: 'Full Disclosure'
Subject: Re: [Full-Disclosure] Caching a sniffer

Hi,

I wonder whether it would be feasible to build network cards that could
report the signal reflection characteristics of the link to make it
possible to detect sniffing equipment cut into a network cable (should
catch magnetic coupling as well).

I bet some security conscious folks will pay lots of $$$ for that.

   Simon

--
GPG Fingerprint: 040E B5F7 84F1 4FBC CEAD  ADC6 18A0 CC8D 5706 A4B4