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/07/31 13:49:00 UTC
[jira] [Commented] (KARAF-5072) Add setting to ssh server for
forcing a provided key
[ https://issues.apache.org/jira/browse/KARAF-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107329#comment-16107329 ]
ASF subversion and git services commented on KARAF-5072:
--------------------------------------------------------
Commit 09d4d1e680524ce6f7dd672287f6aa87c2b60928 in karaf's branch refs/heads/master from [~chris@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=09d4d1e ]
[KARAF-5072] Avoid InterruptedException in case we do not have to wait for started
> Add setting to ssh server for forcing a provided key
> ----------------------------------------------------
>
> Key: KARAF-5072
> URL: https://issues.apache.org/jira/browse/KARAF-5072
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 4.1.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> If karaf does not find a server key in etc/hosts.key it will create one and save it.
> If the key is present but invalid it will be overwritten by default.
> If overwrite=false in the settings and the provided key is invalid then karaf will create a key on every first ssh connect after a restart.
> I think it would be better to have a setting to force the provided key to be used and throw an exception if it is invalid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)