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: <404FF6DA.2060501@onryou.com>
From: lists2 at onryou.com (Cael Abal)
Subject: Caching a sniffer

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ian Latter wrote:

> While there's no way to be sure-sure ... you can get into your
> local LAN segment and send ICMP(/whatever) requests to the
> correct L3 address with the wrong L2 address and see if you
> get a response; this will show you if hosts/devices are listening
> promiscuously (which makes for a good starting point).

Not necessarily?

I thought that depended on the ip stack implementation.

Cael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFAT/baR2vQ2HfQHfsRAgZ0AJ46xhi8rNDXAt5TIHUZL2Il/Lil1gCfeGsE
GiGW9xeSwCMYgGPl1JvLwNE=
=nLkQ
-----END PGP SIGNATURE-----