Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: 0trace - traceroute on established connections |
|---|---|
| Date: | Fri, 28 Sep 2007 11:19:20 -0700 |
On Friday, 2007-09-28 at 11:43 GMT, tyter9@gmail.com wrote:
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?
Remember that the route traffic takes is dynamically determined with each packet - and most of those decisions are made outside your own machine. The path taken by one packet may differ markedly from that of the previous packet to the same destination. And, in trying do what you suggest, you run into all of the shortcomings of traceroute - including: 1. Some nodes won't respond to you. 2. Some nodes may even lie to you. 3. There is no reasonable way to determine the path of the return traffic (asymmetric routing). -- Tony Rall
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: defining 0day, Chad Perrin |
|---|---|
| Next by Date: | [Full-disclosure] [USN-522-1] OpenSSL vulnerabilities, Kees Cook |
| Previous by Thread: | Re: 0trace - traceroute on established connections, tyter9 |
| Next by Thread: | [Full-disclosure] [USN-522-1] OpenSSL vulnerabilities, Kees Cook |
| Indexes: | [Date] [Thread] [Top] [All Lists] |