On Sun, 25 Feb 2001, Ed Wilts wrote:
> I disagree that existing services should be turned off by a freshen. I would
> have hoped that the user settings would be retained. After all, you wouldn't
> expect any other setting to be reset to a pre-defined default either would
> you? Would you be happy if Konqueror decided to change your home page on a
> freshen?
>
> To check the current settings on an existing service is trivial
>
> # chkconfig $SERVICE --list
>
> If it's on when you start the freshen, it should be left on when you finish,
> no matter what the security settings. This is not an "unconscious
> adjustment" - I simply want to leave things the they were before the upgrade.
>
> My security level is set to a recommended level for servers (level 4). I
> have not done any extra customizations other than to turn services on or off.
> This should not mean that I should never upgrade my packages. Even a
> "mandatory" security upgrade for an existing package will disable the
> service, hardly something I would expect Mandrake to enforce on users.
Your suggestion/problem is directly related to msec package. It'd be
better to ask it's developer directly. Sometimes I found it annoying too
(once it gives me segfault). Probably msec is not really complete, or
developers have their reasons. I don't know.
>
> That said, you have pointed me in the right direction and it looks like if I
> manually keep /etc/security/msec/server.4 up to date whenever I turn a
> service on or off, rpm -F seems to perform as expected.
>
>
Good to hear that.
Abel Cheung
