[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 se
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
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/securit
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.$(
using msec-0.17-14mdk
[root@bononcini guillaume]# msec custom
msec: Invalid secure level custom. Use msec.py [0-5] to set it.
--
Guillaume Rousse <[EMAIL PROTECTED]>
GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html