Re: boot/physical security?
Perhaps your /etc/lilo.conf is not putting the boot record where you want it. Do
you have a line in there that says 'boot=/dev/hda' or 'boot=/dev/hda1'? The
former will replace the MBR.
Ian Eure wrote:
> Hi there, just a quick question. As an old slackware user, I usually
> have a restricted boot with a password in my lilo setup, as well as an
> entry for the floppy drive in my system- so, the system boots from drive
> c, hits lilo, and boots linux with the default parameters; if you have
> the password, you can boot from a floppy or give the kernel evtra
> parameters. the bios has a password as well. i found that this was a
> pretty good way to discourage some of the bootfloppy/'linux
> single'/script kiddie hacker-types around my school. however, with
> debian (bo), the actual MBR boot block allows you to boot from a
> different partition, or even a floppy, with no authentication at all-
> even worse, you access it in the same waym by holding down control
> during the boot. I noticed that lilo was setup to use /boot/boot.b as
> default, while slackware always used /boot/any_d.b - but when i tell
> lilo to use any_d.b (verified as being in /boot), it complains loudly
> about not finding my /dev/hda1 - any suggestions?
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
Jens B. Jorgensen
jjorgens@bdsinc.com
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: