Borsenkow Andrej <[EMAIL PROTECTED]> writes:
> � ���, 19.04.2002, � 22:15, Frederic Lepied �������:
> > Borsenkow Andrej <[EMAIL PROTECTED]> writes:
> >
> > > I do not see how to (easily) do it. /etc/security/msec/server.4 is owned
> > > by msec and can thus be overwritten on update.
> > >
> > > Server.{4,5} should be in /var/lib/msec with the possibility to override
> > > them in /etc/security/msec just like with security.conf. I presume that
> > > logic in create_server_link should be
> > >
> > > lf /etc/security/msec/server.LEVEL exists
> > > link /etc/security/msec/server to it
> > > llse
> > > link /etc/security/msec/server to /var/lib/msec/server.LEVEL
> > >
> > > this allows users to override services selection.
> >
> > I don't see the problem here. /etc/security/msec/server.[45] are
> > config files with the noreplace tag so when the package is upgraded,
> > the config files aren't overwritten if they are midified.
>
> Well, but then why do we have /var/lib/msec/security.conf and
> /etc/security/msec/security.conf? Strictly speaking, they are redundant
> as well. I thought it may be some policy behind ...
Because /var/lib/msec/security.conf is written by msec itself each
time you change of security level while the file in
/etc/security/msec/ are just config files that are used by msec but
never changed dynamically.
--
Fred - May the source be with you
