Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why not just use SSH? #4

Closed
MarioVilas opened this issue Feb 20, 2017 · 13 comments
Closed

Why not just use SSH? #4

MarioVilas opened this issue Feb 20, 2017 · 13 comments

Comments

@MarioVilas
Copy link

Or socat, or netcat, or... :)

@MarioVilas
Copy link
Author

Sorry if I come across as rude, I just don't quite imagine a situation where I would need this project instead of the well-known tools...

@Natureshadow
Copy link

I asked myself the same thing :D. What this thing does has existed for years, only that shootback seems to lack all security.

@s1l0uk
Copy link

s1l0uk commented Mar 6, 2017

I would have agreed with you both till last week when I worked with a client who shall remain nameless... they had none of the above installed.

In that situation this would have been very useful
"Here download this and try..." instead of teaching the other admin how to do sockets in python.

Only my humble opiniom - tools on here are offered under opensource license out of the goodness of the developers heart - if you dont need it then dont use it - the community will probably not care ;-)

@Natureshadow
Copy link

Natureshadow commented Mar 6, 2017 via email

@s1l0uk
Copy link

s1l0uk commented Mar 6, 2017

Yeah try doing that when your instances are inside a network and generic packages are not available via yum/apt (ie the infosec team have crippled the yum / apt.d sources for security)

Also how are you going to use SSH when I have blocked it on egress?

I see it as my duty to educate those who have spent too much time in their own environment and dont see the world outside their ivory tower :-)

@MarioVilas
Copy link
Author

MarioVilas commented Mar 6, 2017

I would argue that uploading the netcat binary is much easier than installing a Python program as complex as this one. Also useful in "real life" pentesting (meaning, you don't get to talk to the sysadmin at all, and you don't make changes to the system).

As for the "SSH is blocked" question, you can just move it to another port. I, for one, never set up Internet-facing SSH servers on port 22.

@aploium
Copy link
Owner

aploium commented Mar 6, 2017

Actually, I wrote this because I'm learning python socket programming,
This was my first program in socket operation.
Then I found it useful in some cases, so uploaded it to github.

well, some how, it became popular, I don't know why, maybe many people are facing similar scenario.

For security and production use, you can use ngrok or just SSH -R instead

btw, I had used this in a CTF competition, in that case, SSH and ngrok are not able to handle.

@MarioVilas
Copy link
Author

Thanks for your answer. I had imagined that could be the case, but I wanted to make sure I wasn't missing something here. :)

@zjuchenyuan
Copy link

@MarioVilas For stability, shootback is much better than ncat and SSH
shootback will maintain some not just one connections

@Crapula-Alligator
Copy link

@zjuchenyuan SSH is quite stable for multiple connections. Ncat of course is not.

@Natureshadow
Copy link

Natureshadow commented Mar 14, 2017 via email

@OneB1t
Copy link

OneB1t commented Apr 14, 2019

We needed Tool running stable on Windows server 2008 (just epic... ) And found out that this Is working much better than socat/netcat/portfusion stability on Windows Is much better

Ssh Is pain on Windows environments...i can see why this Is si popular Its a nice project

@DaMatrix
Copy link

ssh tunnels will have congestion issues when handling lots of connections (since it's all transferred through a single TCP socket), whereas this allows individual congestion control for each session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants