mailing list archives
Re: Adding new payloads
From: Ty Miller <tyronmiller () gmail com>
Date: Thu, 27 May 2010 09:37:18 +1000
Solved. I think it was just Windows 7 permissions screwing with me.
I was copying the files in using cygwin bash shell running as a normal user,
which meant that Metasploit couldn't see the files when running as an
I started over, and ran the cygwin bash shell as an administrator, copied
the files across, added HD's suggestion of handler_type_alias, and then
started Metasploit as an admin. Searched for my payload, and it was there.
Thanks for your help.
On Thu, May 27, 2010 at 8:09 AM, Ty Miller <tyronmiller () gmail com> wrote:
If it makes any difference, I'm using win7 with msf3.3. Any other help
would be appreciated.
On Wednesday, May 26, 2010, <tyronmiller () gmail com> wrote:
Unfortunately ~/.msf3/logs/framework.log is empty, but thanks for the
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).
On , HD Moore <hdm () metasploit com> wrote:
On 5/24/2010 7:28 PM, Ty Miller wrote:
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: