On Sunday 03 February 2002 05:51 pm, you wrote: > Pixel <[EMAIL PROTECTED]> writes: > > David Eastcott <[EMAIL PROTECTED]> writes: > > [...] > > > > 2. libmsec.py is removing password but it is not testing for or > > > removing restricted from lilo.conf. What security/msec level actually > > > causes this code to be executed? Or is it disabled? > > > > fredl? > > No the password stuff in lilo/grub is inactive. What make you think > something is done by libmsec ?
In mdk 8.1, msec was removing and adding password to the lilo.conf that was causing grief. Pixel made a change to Drakx that compensated for it. So when I encountered problems with password and restricted this time around I grep'd msec for password. Up came a hit on libmsec and an inspection of the file showed that there was some code in place for deleting password from lilo.conf. Since changing msec levels up and down at the console did not generate any messages indicating msec was modifying lilo.conf, I thought I would ask if it was active and to point out that the code that is in place has a potential problem if it were to be activated. regards Dave
