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.




Network Security FullDisclosure
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: [Full-Disclosure] Odd packet?

from [full-disclosure] Network Security [Permanent Link]
Subject: RE: [Full-Disclosure] Odd packet?
Date: Fri, 28 May 2004 06:13:51 -0700 
Ok.  It seems the case described.  A spoofed packet with your 
IP as the source tries to connect to the compromised machine 
to port 80 at localhost.  The compromised machine doesn't have a
webserver listening at 127.0.0.1:80 so the tcp stack replyes 
ACK RST and sends this packet to your spoofed address.



Unlikely.  If this were the case, the server would reply with RST, not
RST, ACK.  There's too little information to come to any conclusion at
this point.
[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Full-Disclosure] [FLSA-2004:1207] Updated cvs resolves security vulnerability, Jesse Keating
Next by Date:  [Full-Disclosure] Re: Bypassing "smart" IDSes with misdirected frames? (long and boring), Jim Bauer
Previous by Thread:  Re: [Full-Disclosure] Odd packet?, Skip Duckwall
Next by Thread:  RE: [Full-Disclosure] Odd packet?, full-disclosure
Indexes:  [Date] [Thread] [Top] [All Lists]