bugtraq - Re: [Full-disclosure] 0trace - traceroute on established connections

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.58.0701091211000.22436@dione>
Date: Tue, 9 Jan 2007 12:11:49 +0100 (CET)
From: Michal Zalewski <lcamtuf@...ne.ids.pl>
To: Alessandro Dellavedova <alessandro.dellavedova@...m-ieo-campus.it>
Cc: bugtraq@...urityfocus.com, full-disclosure@...ts.grok.org.uk
Subject: Re: [Full-disclosure] 0trace - traceroute on established connections

On Tue, 9 Jan 2007, Alessandro Dellavedova wrote:

> am I wrong or the mechanism that you implement is similar to the one
> implemented in lft (Layer Four Traceroute http://pwhois.org/lft/ ) ?

No, what you describe is similar to tcptraceroute, from what I understand
(they use stray SYNs or RSTs or other TCP packets to do a regular
traceroute).

/mz