Running the provider without a private_key in auth no longer produces a runtime error.
Also, when provided password-authentication takes precedence over ssh-socket-authentication. Since ssh-socket-auth is automatically added, it might block authentication otherwise, when the host doesn't exist there.
Running the provider without a
private_key
in auth no longer produces a runtime error.Also, when provided password-authentication takes precedence over ssh-socket-authentication. Since ssh-socket-auth is automatically added, it might block authentication otherwise, when the host doesn't exist there.
Fixes #12