![]() ![]() ![]() You will configure the site in WinSCP like below. The recommendation is to use Pagent for public key authentication to the server. When you do this using the Local Proxy Command, you cannot use any sort of interactive authentication, so if you're using password authentication when connecting to you will need to specify the password to plink using the -pw switch. The first hop will use the Local Proxy Command and plink to connect to, the second hop will use the Tunnel to connect to and the final connection to is defined as the actual host of the site in WinSCP. Since you're wanting to use WinSCP, this isn't as straight forward since you can only define a single SSH Tunnel in your WinSCP site settings but it is doable by using a Local Proxy Command and then defining an SSH Tunnel in the site's settings in WinSCP. Then you would just connect by using the command ssh final-server. This is assuming you are using key based authentication. If you were just wanting to SSH into using the command-line, you could easily setup your user's ssh config file ~/.ssh/config like so. connects to the final server as user anotheruser.can only be connected to from the server. In this example we are trying to connect to server as the user anotheruser but the machine we're using cannot directly connect to it, only the server can directly connect to it, but we're also unable to connect directly to. This situation might not come up all that too often, but I found one instance where I needed to do it, so this is a quick write up on how to perform a two tunnel hop using WinSCP so you can easily do a file transfer to a remote server you can't directly access. ![]()
0 Comments
Leave a Reply. |