Allow SSH authentication with pubkey
When using SSH runner to connect to a remote server it would be great to use pubkey authentication. My suggestion would be to allow more options for the ssh-config, example keyfile
to add a specific key.
Do not update/delete: Banner broadcast message test data
Do not update/delete: Notification broadcast message test data
When using SSH runner to connect to a remote server it would be great to use pubkey authentication. My suggestion would be to allow more options for the ssh-config, example keyfile
to add a specific key.
It can be done. I guess that it will land in next release (after today's).
Added improvement label
Milestone changed to v0.4.0
The support for identity_file
for ssh
executor is in Bleeding Edge and it will get shipped with 0.4.0
.
Status changed to closed
The best it would be if you would implement the same behaviour as openssh: transparently trying to load the keys from default locations, respecting this order:
debug2: key: /local/home/gitlab_ci_multi_runner/.ssh/id_rsa (0x7f4b5f9043b0),
debug2: key: /local/home/gitlab_ci_multi_runner/.ssh/id_dsa ((nil)),
debug2: key: /local/home/gitlab_ci_multi_runner/.ssh/id_ecdsa ((nil)),
debug2: key: /local/home/gitlab_ci_multi_runner/.ssh/id_ed25519 ((nil)),
As note: I observed that if I write '~/.ssh/id_rsa' it will fail to load the key, probably because you do not expand the home directory in the path.
To maximize the UX, i would say that the registration wizard should allow empty password and it should also say that by default it will try to load the private keys from the default locations in ~/.ssh/(id_rsa|ids_dsa|...)
mentioned in issue #178 (closed)
mentioned in issue #263 (closed)