[
https://issues.apache.org/jira/browse/KARAF-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated KARAF-1505:
---------------------------------------
Fix Version/s: (was: 3.0.0)
3.1.0
Moving to 3.1.0 as you can use unix ssh or putty in production. So this is not
essential for Karaf 3.0.0
> Add a -i option for bin/client and ssh:ssh command to specify a private key
> to use
> ----------------------------------------------------------------------------------
>
> Key: KARAF-1505
> URL: https://issues.apache.org/jira/browse/KARAF-1505
> Project: Karaf
> Issue Type: Improvement
> Reporter: Guillaume Nodet
> Assignee: Christian Schneider
> Fix For: 3.1.0
>
>
> bin/client and ssh:ssh by default use a fixed private key that is deployed in
> the karaf.ssh jar. To use public key auth in a secure way this key needs to
> be exchanged by the user.
> We should have a default location for a private key file that is used instead
> of the built in private key if it exists. Additionally the -i option should
> allow to specify a path to an alternative private key file.
> The default location for the privat key should be ~/.sshkaraf/id_dsa and
> etc/id_dsa
--
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
