evilpacket
Not working.
it hasn't been tested in a long time, I'll take a look when I can get a chance.
Any other feedback other than not working? A stack trace or any other debug that could be useful?
On Wed, Jan 25, 2017 at 4:14 PM, Rocco Musolino [email protected] wrote:
Seems not to be working on Node v.6.2.2.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/evilpacket/node-shells/issues/2, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHEOdmHn2oQHT4RXnV9zlJcfwFiHunZks5rV-V1gaJpZM4LuKWm .
Sorry @evilpacket didn't knew if this repo were still mantained.
Anyway. The issue basically is that if i run the 2 files, the input provided stdin/stdout are not piped to the other process through the socket .. even though the connection is enstablished.
btw 3 Things:
- Why the two files
node_bindshell.jsandnode_revshell.jsboth have a different PORT hardcoded? - Why are the 2 files kept separeted and then again duplicated inside the index.js?
If I run nc -klvp 1337 and then I run node_revshell.js on the port 1337, it works.
If I run node_bindshell.js and then i do nc 127.0.0.1 1337 it works too.
But using those files without nc being involved doesn't work.
No worries. Just don't use it frequently. :). I'll check out your comments tomorrow and see if I can fix.
On Jan 25, 2017, at 4:27 PM, Rocco Musolino [email protected] wrote:
Sorry @evilpacket didn't knew if this repo were still mantained. Anyway. 3 Things.
Why the two files node_bindshell.js and node_revshell.js both have a different PORT hardcoded? Why are the 2 files kept separeted and then again duplicated inside the index.js? I think the issue is in the node_bindshell.js. If I run nc -klvp 1337 and then I run node_revshell.js on the port 1337, it works. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
@roccomuso ok to answer some questions.
-
node_bindshell.js and node_revshell.js are just examples. they are not actually used. They are not meant to be used together.
-
I'm basically a horrible project maintainer and this is just some crap laying around as far as I can tell.
You need something listening on the other end. I only provide the end to be instantiated on the one end. Could use some work maybe but yeah they aren't really mean to be used together (at least that wasn't my intention when it was first made)
Alright, btw they could be used together, but there are some changes to be done. Like these one: Node-reverse-shell
I'm happy to accept PR's for it. I just never thought of that before ha. I mean they should work together just never bothered to try that.
On Wed, Feb 8, 2017 at 3:54 AM, Rocco Musolino [email protected] wrote:
Alright, btw they could be used together, but there are some changes to be done. Like these one: Node-reverse-shell https://gist.github.com/roccomuso/123b5d1ee82b80c1ede0d9c9a1509767
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/evilpacket/node-shells/issues/2#issuecomment-278308148, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHEOTQzTT95hPqV4nCNPtrQgnYEvoa1ks5raa0LgaJpZM4LuKWm .