sshd does not start/stop when enabled/disabled

[bbjimmy]

hrev 51880 sshd does not start/stop when enabled/disabled /boot/system/data/deskbar/menu/Preferences/Network

It seems like the network services file, /boot/system/settings/network/services is only read on boot.

if one kills a running daemon, /bin/sshd it is not re-launched.

My guess is that this is due to recent changes in the launch daemon.

[kallisti5]

The openssh haikuports package needs "daemon users" sshd added. We also need to make sure sshd isn't enabled by default.

[waddlesplash]

Remaining issues tracked in #14382.

[diver]

Seems like this issue is still valid.

[Coldfirex]

Related: https://dev.haiku-os.org/ticket/17127

[Coldfirex]

Milestone needs to be updated. Also I would change the priority to Normal from high. Yes, SSH is enabled by default but it requires further steps for it to be usable.

[bbjimmy]

it now seems to work, although the Netwprl Preferences app does not update treeview view all the time.

[kallisti5]

I think the cause of this one was https://dev.haiku-os.org/ticket/14382. We might be able to close this one now?

[kallisti5]

The SSHD network_settings add-on seems incomplete. Looking at src/add-ons/network_settings/sshd, it "Creates a sshd user if it doesn't exist" and uses a BNetworkServiceSettings to launch it.

I feel like this should be migrated over to a launch_roster service? The net-misc/openssh package should also likely contain a launch config along the lines of:

target desktop {
    service x-vnd.sshd {                                                                         
        launch /bin/sshd -D
        on network_available
    }
}                                                                                    

which is disabled at installation of the openssh package.

Then, the ssh network service preflet addon would look for the presence of "x-vnd.sshd" and enable / disable it to control the service (and optionally update the system's sshd.config)

[kallisti5]

See #18823 for discussion. Essentially today sshd is launched via our net_server in an inetd-like fashion.

Consensus seems to be there's a lot of positive "reduced memory / cpu footprint" considerations continuing to do inetd-like launching of sshd.