Open GoogleCodeExporter opened 9 years ago
Ok, so let me ask--what options would you like this brute force dialog to ask
you for? I've entertained this possibility before but always end up thinking
that you're better off running the module directly because it gives you all of
the options you might need.
Original comment by rsmu...@gmail.com
on 14 Nov 2011 at 3:32
The exact same options as when launching the module directly :)
I requested adding such a menu for convenience sake.
I also like the fact that Armitage makes it easier for Metasploit users to
"explore" and "discover" all the framework's features. Auxiliary modules,
especially scan and bruteforce ones are important components of the framework
(at least bruteforcing always worked for me in large penetration tests). So in
my opinion these modules deserve more highlighting in Armitage.
Original comment by brahim.s...@gmail.com
on 14 Nov 2011 at 7:22
Donnow if it helps, but the auto_brute.rc resource script commited recently
automates the bruteforce process for discovered services.
Original comment by houcem.h...@gmail.com
on 15 Feb 2012 at 9:14
@Houcem hail to the brute baby! Ok, bad joke. You weren't kidding about
recently added. This thing had to make it in, what 24 hours ago? I took a look
at it and it's not suitable for exposing through Armitage yet. Mainly because
it just launches a mass brute force without giving the user any control over
the process.
Once Armitage is scriptable, I envision a reasonable auto-brute option as one
of the things to be added. I think this belongs in the default feature set of
Armitage.
Original comment by rsmu...@gmail.com
on 15 Feb 2012 at 11:49
Some progress has been made in this area. A lot of this is from awhile ago, but
here's what I've got:
1. [host] -> Login -> XXXXX gives you the option to check all credentials
against a host/service.
2. I've added the ability to import credentials to the creds table from Cobalt
Strike
This has pretty much satisfied my personal brute forcing needs. Any other ideas?
Original comment by rsmu...@gmail.com
on 5 Feb 2013 at 8:59
Original issue reported on code.google.com by
brahim.s...@gmail.com
on 14 Nov 2011 at 9:43