[Feature Request] - Support UseKeychain in ssh config file about termscp HOT 6 CLOSED

Hi, unfortunately, I've been really busy recently, so the release of 0.8.1 has been quite delayed. I hope to find the time to work on the last developments in order to release this version.

from termscp.

It sounds cool, but I would take another approach, to be honest.

For architectural reasons, I don't think this is possible to be implemented in the ssh client, but this may be a chance to implement something which is still missing and which would make sense. Probably I've never thought about it since I basically never use the CLI argument to connect, but I'm glad that someone uses them.

A better approach here would be to add a new flag to the CLI options (such as -b) which would tell termscp that the hostname is not an address to resolve, but a bookmark name. In this case, you would be able to save the connection parameters along with the password as a bookmark with a name (e.g. foo) and then automatically connect with termscp -b foo.

Since the password argument is used, if necessary, to unlock an encrypted ssh key, this would solve the issue I guess.

from termscp.

 The main issue is I haven't been able to use termscp at all because it doesn't seem to cooperate with my environment. Or maybe I just don't fully understand it? Like I mentioned, I can ssh my_host and it connects using the fields from my config file and ssh-agent. All of my IdentityFiles are also password protected, which is where UseKeychain comes into play.

I guess my big question then is, how does termscp use the config file? It doesn't seem to read it for the SSH Keys pane or "bookmarks" which I might have hoped it would add the Hosts. It seems to read it right when I go to connect from the UI, but if UseKeychain is in the file, it errors with: IO error (Could not parse configuration file: unknown field: UseKeychain

From someone who has an well defined ssh environment, termscp seemed like it would be a nice addition to my toolkit. If it's not able to use my already defined environment and requires modifying and redefining everything that makes me sad :(

from termscp.

There's an issue with ssh2-config, which doesn't recognize UseKeychain since it was not listed in the Unix manual (because it's available only on macos). I need to patch this in ssh2-config and then update termscp.

from termscp.

Fixed in 0.8.1 branch, due to ssh2-config updated to 0.1.3

from termscp.

Hi @veeso, any chance for a release of 0.8.1?

from termscp.