You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2015/04/20 15:36:58 UTC

[jira] [Closed] (KARAF-1627) Remove sshd command and instead make sshd react directly to config changes

     [ https://issues.apache.org/jira/browse/KARAF-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider closed KARAF-1627.
--------------------------------------
    Resolution: Won't Fix

> Remove sshd command and instead make sshd react directly to config changes
> --------------------------------------------------------------------------
>
>                 Key: KARAF-1627
>                 URL: https://issues.apache.org/jira/browse/KARAF-1627
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-shell
>            Reporter: Christian Schneider
>             Fix For: 4.0.0.M3
>
>
> Currently the start of sshd is controlled using
> "system.properties" there we have the attribute
> "karaf.startRemoteShell" which can be true or false. The problem with this is that changes do not make sshd react directly. You have to restart karaf.
> So we have the sshd command which can also start the ssh server. The problem with the command is that it can only start the server but not stop it. It also start a new server with each call.
> I propose we remove the sshd command and instead move the attribute to control the start into org.apache.karaf.shell.cfg. This is already read using config admin and changes are reflected in real time. 
> I propose the attribute sshdStart=true|false with default to true.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)