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 2012/07/05 11:05:35 UTC
[jira] [Created] (KARAF-1627) Remove sshd command and instead make
sshd react directly to config changes
Christian Schneider created KARAF-1627:
------------------------------------------
Summary: 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
Assignee: Christian Schneider
Fix For: 3.0.0
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 sshd.start=true|false with default to false.
--
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
[jira] [Updated] (KARAF-1627) Remove sshd command and instead make
sshd react directly to config changes
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated KARAF-1627:
---------------------------------------
Description:
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 false.
was:
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 sshd.start=true|false with default to false.
> 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
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> 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 false.
--
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
[jira] [Comment Edited] (KARAF-1627) Remove sshd command and
instead make sshd react directly to config changes
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407029#comment-13407029 ]
Christian Schneider edited comment on KARAF-1627 at 7/5/12 12:11 PM:
---------------------------------------------------------------------
Thx for the information. I was not aware that these system prorperties are controlled by the start script. Looking into the karaf.bat script I found that the ssh server is started for all modes except for client. On the other hand client.bat does not seem to call karaf.bat. So I am not sure what the use case for calling karaf client is. In case this is only old code we could remove the karaf.startRemoteShell properties and control the sshd behaviour like I proposed. Of course switching off the ssh server using the config will make the client not work anymore but I guess that is ok for people.
was (Author: chris@die-schneider.net):
Thx for the information. I was not aware that these system prorperties are controlled by the start script. Looking into the karaf.bat script I found that the ssh server is started for all modes except for client. On the other hand client.bat does not seem to call karaf.bat. So I am not sure what the use case for calling karaf client is. In case this is only old code we could remove the karaf.startRemoteShell properties and control the sshd behaviour like I proposed.
> 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
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> 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 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
[jira] [Commented] (KARAF-1627) Remove sshd command and instead
make sshd react directly to config changes
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407003#comment-13407003 ]
Guillaume Nodet commented on KARAF-1627:
----------------------------------------
Be aware that the {{karaf.startRemoteShell}} and {{karaf.startLocalConsole}} system properties are used from within the bin/karaf shell scripts to control the behavior (without being persistent and change the config). I think this needs to be kept this way, so I'm not sure there is much to gain to be able to dynamically start / stop the ssh server, it's really easy to start/stop the bundle instead.
> 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
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> 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 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
[jira] [Updated] (KARAF-1627) Remove sshd command and instead make
sshd react directly to config changes
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated KARAF-1627:
---------------------------------------
Fix Version/s: (was: 3.0.0)
3.1.0
Moving to 3.1.0
> 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
> Assignee: Christian Schneider
> Fix For: 3.1.0
>
>
> 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 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
[jira] [Commented] (KARAF-1627) Remove sshd command and instead
make sshd react directly to config changes
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407029#comment-13407029 ]
Christian Schneider commented on KARAF-1627:
--------------------------------------------
Thx for the information. I was not aware that these system prorperties are controlled by the start script. Looking into the karaf.bat script I found that the ssh server is started for all modes except for client. On the other hand client.bat does not seem to call karaf.bat. So I am not sure what the use case for calling karaf client is. In case this is only old code we could remove the karaf.startRemoteShell properties and control the sshd behaviour like I proposed.
> 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
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> 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 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
[jira] [Updated] (KARAF-1627) Remove sshd command and instead make
sshd react directly to config changes
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated KARAF-1627:
---------------------------------------
Description:
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.
was:
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 false.
> 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
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> 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 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