|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: [suse-security] disable init=/bin/sh?
From: Kurt Seifried (listuser
seifried.org)Date: Wed Oct 11 2000 - 09:34:21 CDT
- Next message: Jan: "[suse-security] Console blanking"
- Previous message: Roman Drahtmueller: "RE: [suse-security] BIND DNS messages"
- Maybe reply: Kurt Seifried: "Re: [suse-security] disable init=/bin/sh?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>* Kurt Seifried wrote on Wed, Sep 27, 2000 at 12:43 -0600:
>> Alas the timeout option is meaningless, ideally setting timeout=0 would
make
>> lilo accept no user input and boot straight to the default OS. perhaps
this
>> is a feature request.
>
>AFAIK this is not 100% true, since they may situations when lilo
>do accept user input, and finally it's hard if the adminitrator
>needs to reboot with boot parameters like "single" or so.
Usually by the time you _need_ to boot into single user mode it's time to
use a recovery disk/cd. I haven't really encountered any situation in the
last few years where lilo being truly secure would have caused me grief,
OTOH I sure wish I could make lilo secure (restricted and passwd are good,
but more would be better). It's a basic C2 security requirement as well, for
good reason.
>oki,
>
>Steffen
-Kurt
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-security-unsubscribe
suse.com
For additional commands, e-mail: suse-security-help
suse.com
- Next message: Jan: "[suse-security] Console blanking"
- Previous message: Roman Drahtmueller: "RE: [suse-security] BIND DNS messages"
- Maybe reply: Kurt Seifried: "Re: [suse-security] disable init=/bin/sh?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]