Skip to main content
Became Hot Network Question
deleted 12 characters in body; edited tags; edited title
Source Link
Ja1024
  • 23.1k
  • 2
  • 58
  • 69

Can When I assume, in a reverse shelluse SSH tunneling, can I assume that the server does not need to be trusted?

I'm evaluating what is the better technique for SSHing into my machines securely, without trusting third parties.

I can connect to my machines through a reverse shellan SSH tunnel, but I need a server in between.

As far as I understood, the target local machine connects to the server through SSH in the reverse modetunneling, that is, it forwards everything from server:port to local:22. This is in the TCP level, so it's equivalent as having an open SSH port in the wild, which is not a problem.

However, can the server do something malicious through this reverse connection? Besides something that anyone with TCP connection could do, is there something tricky that the server can do?

I mean, something publicly known that can be done. Of course there could be exploits on the openssh server/client

Can I assume, in a reverse shell, that the server does not need to be trusted?

I'm evaluating what is the better technique for SSHing into my machines securely, without trusting third parties.

I can connect to my machines through a reverse shell, but I need a server in between.

As far as I understood, the target local machine connects to the server through SSH in the reverse mode, that is, it forwards everything from server:port to local:22. This is in the TCP level, so it's equivalent as having an open SSH port in the wild, which is not a problem.

However, can the server do something malicious through this reverse connection? Besides something that anyone with TCP connection could do, is there something tricky that the server can do?

I mean, something publicly known that can be done. Of course there could be exploits on the openssh server/client

When I use SSH tunneling, can I assume that the server does not need to be trusted?

I'm evaluating what is the better technique for SSHing into my machines securely, without trusting third parties.

I can connect to my machines through an SSH tunnel, but I need a server in between.

As far as I understood, the target local machine connects to the server through SSH tunneling, that is, it forwards everything from server:port to local:22. This is in the TCP level, so it's equivalent as having an open SSH port in the wild, which is not a problem.

However, can the server do something malicious through this reverse connection? Besides something that anyone with TCP connection could do, is there something tricky that the server can do?

I mean, something publicly known that can be done. Of course there could be exploits on the openssh server/client

edited title
Link
Steffen Ullrich
  • 207.6k
  • 30
  • 416
  • 481

Can I assume, in a reverse shell, that the server isdoes not need to be trusted?

Source Link
aaa
  • 163
  • 1
  • 5

Can I assume, in a reverse shell, that the server is not trusted?

I'm evaluating what is the better technique for SSHing into my machines securely, without trusting third parties.

I can connect to my machines through a reverse shell, but I need a server in between.

As far as I understood, the target local machine connects to the server through SSH in the reverse mode, that is, it forwards everything from server:port to local:22. This is in the TCP level, so it's equivalent as having an open SSH port in the wild, which is not a problem.

However, can the server do something malicious through this reverse connection? Besides something that anyone with TCP connection could do, is there something tricky that the server can do?

I mean, something publicly known that can be done. Of course there could be exploits on the openssh server/client