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: <20070928114359.17135.qmail@securityfocus.com>
Date: 28 Sep 2007 11:43:59 -0000
From: tyter9@...il.com
To: bugtraq@...urityfocus.com
Subject: Re: 0trace - traceroute on established connections

I think it would be interesting to enumerate incoming connections. 

user (192.168.0.2) --> router (192.168.0.1) --> gateway/masquarade --> ~~~~ --> server (0trace).
What do you think about it? is it possible to enumerate internal "user" user network? 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ