Added support to directly use socket object instead of giving ip.

[nkpro2000sr]

your project is really useful for me so please merge my pull request or make changes yourself. unfortunately i can't add this support in your smbclient branch. For_more_details_see_this

[jborean93]

So reading through you markdown file it looks like you are starting your own socket outside of pypsexec or smbprotocol and then wanting to pass that into one of those libraries to use as the underlying transport. What extra steps are you doing when starting that socket before you pass it in?

You say you can't add this to your smbclient branch is there a reason why? If it's because the branch no longer exists that's because the chagnes are in the master branch so you just need to create a new one off master and create a pull request for that. If we do go ahead with this, it will most definitely need some work in smbprotocol as I don't want to maintain 2 copies of connection.py.

[nkpro2000sr]

Reply to :"What extra steps are you doing when starting that socket before you pass it in?" I have to make connection from remote machine to me using SSH Server remote port forwarding, for that i create socket object listening in specific port which after established connection from remote machine pass to pypsexec. As i am not able to start SSH remote port forwarding in remote machine i have to listen on my side and connection from remote machine.

I can't add this in your smbclient branch because it needs lot of changes in both your smbprotocol and smbclient package.

and If you like we can go ahead, but first i don't know much about smbprotocol.