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-next>] [day] [month] [year] [list]
Message-ID: <F509E6111989D311B63700805FA761DA0D20AC9B@DBDE01>
From: motiwala at ti.com (Motiwala, Yusuf)
Subject: Caching a sniffer

TDR will not work if someone running Sniffer on existing network port.
Isn't?

Yusuf


> -----Original Message-----
> From: full-disclosure-admin@...ts.netsys.com [mailto:full-disclosure-
> admin@...ts.netsys.com] On Behalf Of Dave Horsfall
> Sent: Thursday, March 11, 2004 8:22 AM
> To: Full Disclosure List
> Subject: Re: [Full-Disclosure] Caching a sniffer
> 
> On Wed, 10 Mar 2004, Patricio Bruna V. wrote:
> 
> > How can i know if there a sniffer running in my network?
> 
> When you wake up one day to find that you're 0wn3d :-)
> 
> Seriously, about the only way I can think of to detect a sniffer with
> its transmit leads cut is with a Time Domain Reflectometer (TDR) and
> look for an unexplained impedance bump.
> 
> --
> Dave Horsfall  DTM  VK2KFU                         Loyal Unix user since
> 1975
> Booted from Spamtools for dissing the moderator:
> www.horsfall.org/levine.mail
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ