31–40 of 63 posts
Earlier quoted context omitted.
What do you mean by that?
As an an example, at my work you cannot make any outbound ssh connection. The only way to get one is to apply for a specific connection , where you have to explain why you need an outbound connection, in which case they open a port for you and the remote machine you specified.
Earlier quoted context omitted.
What do you mean by that?
As an an example, at my work you cannot make any outbound ssh connection. The only way to get one is to apply for a specific connection , where you have to explain why you need an outbound connection, in which case they open a port for you and the remote machine you specified.
Odd that the client is written in C, but the server in go. I'm curious as to why the author chose to do that (along with the artisan buffer implementation).
Earlier quoted context omitted.
As an an example, at my work you cannot make any outbound ssh connection. The only way to get one is to apply for a specific connection , where you have to explain why you need an outbound connection, in which case they open a port for you and the remote machine you specified.
if it's just filtering of certain ports, you can just set your ssh port to 80 or 443
Earlier quoted context omitted.
What do you mean by that?
As an an example, at my work you cannot make any outbound ssh connection. The only way to get one is to apply for a specific connection , where you have to explain why you need an outbound connection, in which case they open a port for you and the remote machine you specified.
I‘m using ttyd ( https://github.com/tsl0922/ttyd ) behind an nginx reverse proxy with client certificates. This gives me access from locations where ports other than https are blocked.
I‘m using ttyd ( https://github.com/tsl0922/ttyd ) behind an nginx reverse proxy with client certificates. This gives me access from locations where ports other than https are blocked.
Yes, you can run `login` instead of a shell, but doing so require the tool to be executed as root, still sound bad.
I'd recommend to use a proxy that supports converting socket to Websocket(wss) and back, then you can by-pass the blockage from there. And since it's a proxy, it should not decrypt the SSH traffic.
Why not just use SSH?
Earlier quoted context omitted.
As an an example, at my work you cannot make any outbound ssh connection. The only way to get one is to apply for a specific connection , where you have to explain why you need an outbound connection, in which case they open a port for you and the remote machine you specified.
if it's just filtering of certain ports, you can just set your ssh port to 80 or 443
Anything more sophisticated will inspect the traffic and drop SSH connections no matter the port.
Earlier quoted context omitted.
What do you mean by that?
As an an example, at my work you cannot make any outbound ssh connection. The only way to get one is to apply for a specific connection , where you have to explain why you need an outbound connection, in which case they open a port for you and the remote machine you specified.
If not, then this seems like an exfiltration risk your security people should fix.