Home page logo
/

metasploit logo Metasploit mailing list archives

Re: Adding new payloads
From: tyronmiller () gmail com
Date: Tue, 25 May 2010 22:39:09 +0000

Unfortunately ~/.msf3/logs/framework.log is empty, but thanks for the tip.

I added the handler_type_alias code to the payload stager module, but still no love.

If it helps, I'm using the reverse_https payload files as a basis to work from. So I copied the following files and renamed them to be those listed in my first email, then went through and modified relevant references to https to point to mypayload (mainly the handler stuff).

./msf3/external/source/shellcode/windows/x86/src/stager/stager_reverse_https.asm
./msf3/external/source/shellcode/windows/x86/src/block/block_reverse_https.asm
./msf3/modules/payloads/stagers/windows/reverse_https.rb
./msf3/lib/msf/core/handler/reverse_https.rb

Thanks,
Ty


On , HD Moore <hdm () metasploit com> wrote:
On 5/24/2010 7:28 PM, Ty Miller wrote:

> ./msf3/modules/payloads/stagers/windows/reverse_mypayload.rb

> ./msf3/lib/msf/core/handler/reverse_mypayload.rb

>

> Do I need to do anything else to get it to appear in msfconsole when I

> search for mypayload?



In the payload stager module, you need to set a unique alias for your

stager. Otherwise it will use its parent class's alias (reverse_tcp) and

conflicts with the existing stager.



This looks like:





def self.handler_type_alias

"reverse_awesome_tcp"

end





-HD

_______________________________________________

https://mail.metasploit.com/mailman/listinfo/framework

_______________________________________________
https://mail.metasploit.com/mailman/listinfo/framework

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]