Bugtraq mailing list archives
Re: obsd boot hack (boot-modified-kernel-attack)
From: deraadt () CVS OPENBSD ORG (Theo de Raadt)
Date: Tue, 14 Apr 1998 17:39:10 -0600
You don't even need such a complicated kernel modification program to do this:
boot -d
Voila, you are in the kernel debugger. Or, alternatively, make your own root filesystem and do:
boot -a
[...] root device? fd0a
and create the file /etc/boot.conf and add a line
boot bsd
This will cause the system to automaticly boot and load
the /bsd kernel with out issueing the user the option to
load a alternitive kernel.
That's the suggested way of handling secure machines. I'm not sure if we want to put a password system in there, it isn't clear if it will help. We'll think about it.
Current thread:
- Symlink problem (Tested only on a Digital Unix 4.0) root (Apr 06)
- Re: Symlink problem (Tested only on a Digital Unix 4.0) Jonathan A. Zdziarski (Apr 06)
- <Possible follow-ups>
- Re: Symlink problem (Tested only on a Digital Unix 4.0) Paul Szabo (Apr 06)
- Re: Symlink problem (Tested only on a Digital Unix 4.0) John McDonald (Apr 07)
