unable to authenticate using public keys for ssh runners

I was surprised to discover that public key authentication is not possible using the ssh runners.

Build failed with ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain

Public key authentication is the defacto way of using ssh and should be enabled and preferred by default. Based on the error message I suspect that it is disabled on purpose.

This is a blocker issue because we do have the password authentication disabled on SSH on all servers, as that's a recommended security practice.

Milestone changed to v0.4.0

Status changed to closed

It's available in latest bleeding edge: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md#the-runnersssh-section

Thank you. I switched to the bleeding edge version and will be running this one and hopefully I will be able to provide useful feedback.

For the moment I am surprised that there is no command that would show me the status, something regarding how many runners are running. Also I discovered that the executable does not acts as a real service controller like the gitlab-ctl, meaning that if I run it from another directory, while logged in as root, it will not load the config.toml from the gitlab-ci-multi-runner home directory.

Also because I am using Debian, I was expecting to see it as a service, so I could use it the standard command service xxx start/stop/....

If you install it from .deb package it will automatically install as service allowing you to use service xxx start/stop. There's nothing similar to gitlab-ctl currently, but it may be added in future.