Bug 535206

Summary: sshd not started by default in installation over vnc or ssh
Product: [openSUSE] openSUSE 11.2 Reporter: Per Jessen <per>
Component: YaST2Assignee: Katarina Machalkova <kmachalkova>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P2 - High CC: binner, lnussel, thomas, zadeck
Version: Milestone 6Flags: coolo: SHIP_STOPPER+
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: patch for yast2-firewall
patch for yast2-network

Description Per Jessen 2009-08-28 15:18:35 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.8.1.6) Gecko/20070730 SUSE/2.0.0.6-25 Firefox/2.0.0.6

I did an SSH+HTTP installation of M6 and disabled the firewall as I always do.  I was a bit surprised to find that sshd was now no longer automatically started.  I'd like to suggest that ssh is enabled by default when installation is done via vnc or ssh where there is often no physical access to the server.

Reproducible: Always
Comment 2 Thomas Schulte 2009-09-13 22:53:46 UTC 
I did a "normal" installation of M7 and got the same problem. The sshd service was turned off by default.
Comment 3 Stephan Kulow 2009-09-14 13:54:28 UTC 
#2 is basically a missing feature, #0 is a bug
Comment 4 Ludwig Nussel 2009-09-16 13:28:48 UTC 
so yast needs to make sure sshd is enabled if it detects an install via vnc or ssh.
Comment 5 Stephan Kulow 2009-09-16 15:04:45 UTC 
perhaps sshd shouldn't have been turned off without any discussion with yast developers?
Comment 6 Ludwig Nussel 2009-09-22 08:29:10 UTC 
I'm currently testing two patches to yast2 to enable sshd if ssh install mode was selected or the user chooses to open the port.
Comment 7 Ludwig Nussel 2009-09-22 13:51:46 UTC 
Created attachment 319304 [details]
patch for yast2-firewall
Comment 8 Ludwig Nussel 2009-09-22 13:52:20 UTC 
Created attachment 319305 [details]
patch for yast2-network
Comment 9 Ludwig Nussel 2009-09-22 14:31:20 UTC 
patches look good so far, Katarina could you review and commit them? Thanks
Also fixes bug 537980
Comment 10 Katarina Machalkova 2009-09-29 09:36:18 UTC 
Should be fixed in milestone8
Comment 11 kenneth zadeck 2009-11-15 18:52:28 UTC 
I have now 3 installs of the released version of suse 11.2 on x86-64 from a dvd.   In all of them, the sshd has not been started. 

In a related area, using the yast2 sshd config is completely useless, because while it allows you change the parameters, it does not bother to tell you that it is actually not starting the server or that the server has not been set to automatically be started.

If you want me to make any of these separate bugzillas, i will do so.

kenny
Comment 12 Katarina Machalkova 2009-11-18 13:27:50 UTC 
(In reply to comment #11)
> I have now 3 installs of the released version of suse 11.2 on x86-64 from a
> dvd.   In all of them, the sshd has not been started. 

For SSH to start on boot you have to either 1) install remotely over SSH or 2) in the installation proposal (firewal and SSH section) opt for opening SSH port on firewall and starting SSH service

> In a related area, using the yast2 sshd config is completely useless, because
> while it allows you change the parameters, it does not bother to tell you that
> it is actually not starting the server or that the server has not been set to
> automatically be started.

Please file a separate bugzilla ticket for this one - yast2-sshd should (alike to other server config modules) support setting when (and if) the service (SSH) should be started
Comment 13 kenneth zadeck 2009-11-18 13:42:10 UTC 
I figured the first part of this out after filing the bugzilla.   It is somewhat anoying because (1) this is a difference from prior releases and (2) the part of the install config screen that contains the info requires scrolling down.  

The second part is filed as bugzilla 556535.