Metasploit mailing list archives
db_autopwn: Determining what exploit gained a shell
From: hdm at metasploit.com (H D Moore)
Date: Sat, 12 May 2007 13:22:37 -0500
Yup, theres a reason :-) Since this feature can launch modules against every type of OS or CPU supported by the framework, we need to pick the lowest common denominator for the payload options (bind, reverse). Nothing stops us from adding a method of specifying individual payloads for every unique OS/CPU combination, but it hasn't been implemented yet. -HD On Saturday 12 May 2007 11:28, nnp wrote:
Erm... right.... I probably should have mentioned I was talking about db_autopwn. As in is there payload besides the -r and the -b options that's available through db_autopwn and if there isn't is there a reason why there isnt besides nobody getting around to it yet?
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)