Mailinglist Archive: opensuse-bugs (15049 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=326480

           Summary: yast2 sshd module doesn't modify sshd_config at the
                    right places
           Product: openSUSE 10.3
           Version: Beta 3
          Platform: All
        OS/Version: openSUSE 10.3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
        AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: funtasyspace@xxxxxxxxx
         QAContact: jsrain@xxxxxxxxxx
          Found By: ---


In the default sshd config file (/etc/ssh/sshd_config) most options are
commented out. The ssh daemon will use the internal default values for those
options. The problem is, that the yast2 sshd module

a) doesn't know the default values of the out-commented options
b) doesn't uncomment and write/change those out-commented options at the right
places in the config file.

So if you run the yast2 sshd module the first time after a fresh installation
and default sshd_config file, there are inconsistencies between the gui and the
sshd state. Another problem is, that the yast module doesn't uncomment the
options it can handle in the config file, but writes them as new lines at the
end of the config file. If the user manually uncomments the options yast2 can
handle, everything is fine. Yast2 will change the options at the right places
and will not add them as new lines at the end of the config file. And because
all the option values of a fresh/default config file are equivalent to the
internal sshd default options, the GUI will not be inconsistent during the
first run of the module. Of course this is no convenient solution for users. 

Possible Solutions:
1. Change the openssh package so that in the default sshd_config file the
options yast2 sshd can handle are NOT commented out. This way, yast2 sshd
module is not inconsistent during the first run and it will not add new lines
with options at the end of the config file, but change the existing options at
their right places in the config file (if the user did any). The drawback is,
that the openssh package should be modified each time the yast2 module was
enhanced to handle more options.

2. Let the yast2 sshd module detect out-commented options in the sshd_config
file. 
- If an option is commented out, make the yast2 sshd gui consistent with sshd's
internal default values. I don't know if there is a way to get the default
values from somewhere automatically, or if yast2 has to know them hard coded.
- If the user changes an out-commented options via the yast2 module, uncomment
the corresponding option at the right place in the sshd_config file and set the
value there.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.