You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 bycargo remote
whenssh
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 tocargo remote
and add logic that passes it as-i <file>
tossh
under the hood. Also, it'd be nice to have support to add a setting likeident = <path>
tocargo-remote.toml
file (and cmd line param overwrites it).Marcin
The text was updated successfully, but these errors were encountered: