You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2014/01/09 01:40:50 UTC
[jira] [Commented] (LIBCLOUD-461) fix ssh for servers with
PubkeyAuthentication only
[ https://issues.apache.org/jira/browse/LIBCLOUD-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866119#comment-13866119 ]
Tomaz Muraus commented on LIBCLOUD-461:
---------------------------------------
Corresponding Github pull request: https://github.com/apache/libcloud/pull/194
> fix ssh for servers with PubkeyAuthentication only
> --------------------------------------------------
>
> Key: LIBCLOUD-461
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-461
> Project: Libcloud
> Issue Type: Bug
> Reporter: Markos Gogoulos
>
> On libcloud/compute/ssh.py we specify password OR public key to ssh to a cloud server. This results in deploy_node to fail to ssh to a server where it allows PubkeyAuthentication only (example HPCloud servers).
> However there's no need to specify only one of the two, both can be specified. Paramiko's authentication is attempted in the following order of priority:
> (from paramiko/paramiko/client.py)
> public key(s) passed,
> any key found through an SSH agent,
> any "id_rsa" or "id_dsa" key discoverable in ~/.ssh/,
> plain username/password auth, if a password was given
> I've tried the patch on several backends (including HPCloud) and it worked without issues
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)