Well,
Firstly if the environment is supposed to be a secure environment use
the systems bios to lock the keyboard, if that is not possible, require
a bios password at boot. You might also want to use lilo.On Sat, 2003-01-25 at 01:44, camthompson wrote: > consider this (I'm trying to make a network more secure) : > A user enters grub upon bootup and hits "e" to edit the Linux boot > procedure and then continues to boot into single user mode, and he then > chagnes the root password to whatever he suits.... the user who did this > is eventually tracked down and taken care of. > > Now, how would I prevent this from happening in future instances? -- ATD <[EMAIL PROTECTED]> Secure Network Operations, Inc.
signature.asc
Description: This is a digitally signed message part
