Metasploit mailing list archives
How do I disconnect without causing an exploit to fail
From: justfriends4n0w at yahoo.com (Randy Flood)
Date: Sun, 13 May 2007 06:54:01 -0700 (PDT)
So I am playing around with writing an FTP fuzzer. Right now I am writing it as an exploit, even though eventually I plan to modify it to be an auxillary module or something. Anyway, how to I close the TCP socket that is created by connect_login(true, true) without killing my exploit? Like for example, if I send a "DISCONNECT" verb to the FTP server, it will disconnect me, but the framework will detect that "[-] Exploit failed: An existing connection was forcibly closed by the remote host". I'd like to somehow capture the error generated when the remote host closes my TCP socket rather than crash out. How can I do this? ____________________________________________________________________________________Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469
Current thread:
- db_autopwn: Determining what exploit gained a shell nnp (May 11)
- db_autopwn: Determining what exploit gained a shell mmiller at hick.org (May 11)
- db_autopwn: Determining what exploit gained a shell nnp (May 12)
- db_autopwn: Determining what exploit gained a shell The KiLLeR MaF!a (May 12)
- db_autopwn: Determining what exploit gained a shell nnp (May 12)
- db_autopwn: Determining what exploit gained a shell H D Moore (May 12)
- How do I disconnect without causing an exploit to fail Randy Flood (May 13)
- db_autopwn: Determining what exploit gained a shell nnp (May 13)
- db_autopwn: Determining what exploit gained a shell nnp (May 12)
- db_autopwn: Determining what exploit gained a shell mmiller at hick.org (May 11)