You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2012/05/29 06:31:25 UTC
[dev] [jira] [Closed] (LIBCLOUD-182) Allow ssh_agent and/or password
protected ssh keys in 'deploy_node'
[ https://issues.apache.org/jira/browse/LIBCLOUD-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus closed LIBCLOUD-182.
---------------------------------
> Allow ssh_agent and/or password protected ssh keys in 'deploy_node'
> -------------------------------------------------------------------
>
> Key: LIBCLOUD-182
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-182
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Neil Wilson
> Assignee: Tomaz Muraus
> Priority: Minor
> Fix For: 0.10.1
>
>
> After getting waylaid by incorrect error messages in paramiko, it appears that 'deploy_node' doesn't support either password protected ssh_keys or ssh_agent keys for ssh access.
> So with key access clouds you can only use a non-password protected key that is actually stored on the machine that is doing the deployment.
> ParamikoSSHClient turns off both the SSH Agent and the automatic key search facility. Any particular reason why?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira