Hello,
currently, there is no way to pass to cargo remote via cmd line a path to RSA identity key. This implies the default one (ie in most cases ~/.ssh/id_rsa) is chosen by cargo remote when ssh to a remote server. But sometimes one needs to have the possibility to use a non-default RSA identity file (e.g. user can have more than one such file in ~/.ssh).
Therefore proposed feature would be to add -i <file> cmd line flag to cargo remote and add logic that passes it as -i <file> to ssh under the hood. Also, it'd be nice to have support to add a setting like ident = <path> to cargo-remote.toml file (and cmd line param overwrites it).
Marcin
Hello,
currently, there is no way to pass to
cargo remotevia cmd line a path to RSA identity key. This implies the default one (ie in most cases~/.ssh/id_rsa) is chosen bycargo remotewhensshto a remote server. But sometimes one needs to have the possibility to use a non-default RSA identity file (e.g. user can have more than one such file in~/.ssh).Therefore proposed feature would be to add
-i <file>cmd line flag tocargo remoteand add logic that passes it as-i <file>tosshunder the hood. Also, it'd be nice to have support to add a setting likeident = <path>tocargo-remote.tomlfile (and cmd line param overwrites it).Marcin