Ticket #28 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

When reconfiguring ssh, default behaviour should be to restart sshd on reboot

Reported by: david Owned by: rmcmillen
Priority: minor Milestone: roo-1.4
Component: Walleye Version: 1.4b3
Keywords: Cc:


Using Walleye to change the port sshd runs on has an option to start sshd on reboot. The text suggest that this is sensible (and it is, otherwise you'll get locked out!), but the default check box is unselected. This means anyone who just changes the port will lose remote access after a reboot. It would be sensible for the default behaviour to be "restart sshd on reboot" = checked.

Change History

Changed 11 years ago by rmcmillen

  • owner changed from [email protected] to rmcmillen
  • status changed from new to assigned

The SSH Administration screen decides how to set that checkbox based on the contents of the HwSSHD_STARTUP variable. If the variable does not yet exists, it is blank.

If you return to the page after you have checked and configured the daemon, it should reflect the state of the honeywall.

Maybe what we need to do is add the variable to the configuration you are using to configure your honeywall from install.

This said, the dialog way of configuring the ssh daemon does not ask the user if they want to enable it at startup nor does it use the HwSSHD_STARTUP variable. This should probably be corrected.

Changed 11 years ago by rmcmillen

  • status changed from assigned to closed
  • resolution set to fixed

The box is now checked if HwSSHD_STARTUP is set or if the variable is undefined (See ChangeSet? [53]). The new rpm is: walleye-1.2.6-1.noarch.rpm

Note: See TracTickets for help on using tickets.