[
https://issues.apache.org/jira/browse/LIBCLOUD-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomaz Muraus resolved LIBCLOUD-461.
-----------------------------------
Resolution: Fixed
First to clarify this a bit - before your change, deploy_node method would only
fail if a driver supplied both arguments - "password" and a "key". This would
happen because "password" argument had precedence over "key" argument.
In any case, as noted in the pull request, I've addressed some issues and
merged patch into trunk.
Thanks!
> 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)
