[EMAIL PROTECTED] (Guillaume Rousse) writes: > Ainsi parlait J.A. Magallon : > > On 20020124 Guillaume Rousse wrote: > > >Ainsi parlait J.A. Magallon : > > >> On 20020122 Guillaume Rousse wrote: > > >> >using msec-0.17-14mdk > > >> >[root@bononcini guillaume]# msec custom > > >> >msec: Invalid secure level custom. Use msec.py [0-5] to set it. > > >> > > >> I think you have to edit manually /etc/security/msec/perm.local > > >> It is used after perm.$(LEVEL). > > >> You can add modified permissions there using other perm.X as > > >> templates... > > > > > >I don't have /etc/security/msec/perm.local, but i have > > >/etc/security/msec/perm.snf > > >Anyway, msec admitted a "custom" security level, that was very practical > > > to set different parameters individually. It seems to have vanished... > > > > (don't know if I have sent this already, problems with my ISP...) > > > > No, it does not exist by default. Just create it and put there > > all those permissions that you want different from what the > > standard msec does. > OK, but there *was* a custom option to msec which triggered a list of > question to fill this file for you. I guess it has vanished in the shell -> > python translation. It is planned to reimplement it back, or has it been > volontary dismissed ?
check out the latest version. It is however implemented in some different way. One can add his own commands in the /usr/security/msec/level.local file. There are no step by step questions for the moment ... cheers, -- Florin http://www.mandrakesoft.com
