Metasploit Framework

These sound interesting.

Rob Fuller wrote:

2. Dynamic connection handling
3. Binding for other tool use
4. Daemonizing for multiple connections (wouldn't be much fun having to issue the connect command each time medusa wanted to try a password)

Do you mind elaborating on these though?

For example: any precise requests (implementation or otherwise)? Any interface ideas?

Just whatever is on your mind regarding these.

1. (blank)
2. Dynamic connection handling
   • What would be ideal here is Metasploit actually setting up a fake (or VPN-like) interface that you would route your connections through so it would show up exiting on the distant end's (compromised host) interface (which I can understand won't happen due to compat issues). But I guess the next best thing would be a SOCKS proxy deal like 'ssh -d' does.
3. Binding for other tool use
   • Sort of like the above, except it would be like netcat port-forwarding Attacker -> Compromised Host A -> Host B. This would be useful for things that can't use SOCKS proxies, and for a more targeted approach.
4. Daemonizing for multiple connections (wouldn't be much fun having to issue the connect command each time medusa wanted to try a password)
   • Essentially this feature just keeps anything from closing the connection except for the attacker. Sort of like the mystical netcat -L flag.
5. Upgrade to meterpreter
   • Just wanted to add this one, and yes I know it's beating a dead horse