You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/08/03 08:57:00 UTC

[jira] [Commented] (KARAF-5286) Separate server key generation from key reading

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

ASF subversion and git services commented on KARAF-5286:
--------------------------------------------------------

Commit 549471c74cdf62b1bbcabc2bcb3857f22083f156 in karaf's branch refs/heads/OPENSSH from [~chris@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=549471c ]

[KARAF-5286] Separate server key generation from key reading. Only support openssh pem server keys


> Separate server key generation from key reading
> -----------------------------------------------
>
>                 Key: KARAF-5286
>                 URL: https://issues.apache.org/jira/browse/KARAF-5286
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-shell
>    Affects Versions: 4.2.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 4.2.0
>
>
> Currently we use AbstractGeneratorHostKeyProvider to read server keys and also generate them on the fly. According to the mina sshd team this class is not meant for production use.
> So I propose we create a separate classes for reading and writing keys.
> I also propose we remove the hostKeyFormat config and only support OpenSSH pem based keys.
> For now we need a custom OpenSSHKeyPairProvider to read out keys as mina sshd has a bug (SSHD-760). After the release of sshd 1.7.0 we can switch to the standard FileKeyProvider from mina.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)