Ssh tunnel winscp password#

However, in the (unlikely?) scenario where some machines are accessed by password, and others by key, it might be a bit clumsy, requiring the user to clear the field.

In most cases the user is connecting to the same machine for remote profiling, so the default value in this field will be fine. I assume the path field will have a button that launches an 'Open File' dialog? If the file is specified, it will be used. We can add the second text field below the connection URL:įor SSH: private key file (leave blank if not used): There are pure-Java libraries to do this, used by IDEA for a similar feature (connecting to a remote database over an SSH tunnel).Īnton Katilin wrote:As far as I understand, we'll need to supply the library with the private key file, which is ~/.ssh/id_rsa by default. The idea is to embed this into the YK client, streamlining this use case (which is quite common).

Ssh tunnel winscp password#

* GUI support (in the 'Connect To Remote Application' dialog) to enter an ssh username and password for the remote systemĪt the moment, I can do this manually, by setting up an SSH tunnel from the workstation to the target server, using a command like this, and then connecting to local port 10001: * support to set up and use an SSH tunnel, providing a secure connection over which the client would connect to the agent On the client/GUI side, two things would be implemented:

However, the server is running an SSH deamon. The assumption is that the application is running on a remote server, but the port on which the agent is listening is not accessible from outside. This would rather be a client-side feature, with UI support for configuration.