Metasploit mailing list archives
Using encoders directly
From: mmiller at hick.org (mmiller at hick.org)
Date: Wed, 27 Dec 2006 11:25:28 -0800
On Thu, Dec 21, 2006 at 11:19:56AM -0500, Krpata, Tyler wrote:
I think this question got lost in my last post, so I thought I'd start a new thread about it. Should I be able to use the encoders in Metasploit directly? What I'd like to do is use the Alpha2 encoder something like: payload = Rex::Encoder::Alpha2::UnicodeMixed.encode(shellcode,"EBX",0) The "shellcode" argument in this case is actually the code retrieved from the "egghunter" class.
Apologies for the late reply, I've been out of town. Right now the API that's exposed to encode arbitrary (non-payload) buffers isn't very easy to use. It'd be better if we added a method to the EncodedPayload class that would allow you to specify a buffer rather than a payload instance. With that said, your use of the encode method looks correct. Can you include the actual exception message that's displayed (aside from just the call stack)? That might help narrow down a bit more what's going on.
Current thread:
- Using encoders directly Krpata, Tyler (Dec 21)
- Using encoders directly mmiller at hick.org (Dec 27)
- <Possible follow-ups>
- Using encoders directly Krpata, Tyler (Dec 27)
- Using encoders directly mmiller at hick.org (Dec 27)