You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/05/27 22:11:18 UTC

[jira] [Commented] (KARAF-1505) Add a -i option for bin/client and ssh:ssh command to specify a private key to use

    [ https://issues.apache.org/jira/browse/KARAF-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561625#comment-14561625 ] 

Jean-Baptiste Onofré commented on KARAF-1505:
---------------------------------------------

We already added:

{code}
  -k [keyFile]    specify the private keyFile location when using key login, need have BouncyCastle registered as security provider using this flag
{code}

However, a default location (like .karafssh/id_dsa) is good idea.

> 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
>             Fix For: 4.0.0.M3
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)