Bug#56821: [POSSIBLE GRAVE SECURITY HOLD]
- To: Ruud de Rooij <email@example.com>
- Cc: Joseph Carter <firstname.lastname@example.org>, Martijn van Oosterhout <email@example.com>, Samuel Tardieu <firstname.lastname@example.org>, Adam Di Carlo <email@example.com>, "Huneycutt, Doug" <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Subject: Bug#56821: [POSSIBLE GRAVE SECURITY HOLD]
- From: Thomas Quinot <email@example.com>
- Date: Wed, 2 Feb 2000 15:10:24 +0100
- Message-id: <[🔎] 20000202151024.A3765@cuivre.fr.eu.org>
- Reply-to: Thomas Quinot <firstname.lastname@example.org>, email@example.com
- In-reply-to: <[🔎] firstname.lastname@example.org>; from email@example.com on Wed, Feb 02, 2000 at 02:13:50PM +0100
- References: <[🔎] firstname.lastname@example.org> <[🔎] 389823E6.37B56639@cupid.suninternet.com> <[🔎] 20000202045337.A10828@debian.org> <[🔎] email@example.com>
Le 2000-02-02, Ruud de Rooij écrivait :
> I do agree, however, that it is not a security hole. If someone wants
> to make the console secure, they would have to modify lilo.conf
> anyway, and so could change the boot= line as well.
I feel this behaviour is a security concern, because it opens
a path for root compromission in an obscure, non-standard, non-documented
way. It is very unfortunate that, when installed using default settings,
all floppy boot restrictions can be bypassed on a Debian system, even when
the administrator takes the usual required step consisting in physically
securing the machine's enclosure, disabling floppy boot in the BIOS,
and properly configuring LILO. Introducing one more layer in system startup
is unnecessary, and considering that this layer as configured at system
installation, grants every user root access, /very/ unfortunate.
I am amazed by Debian developers seriously writing that "this is not
a security concern", since we have had evidence of this hole being
actively exploited. Undue root access /has been/ obtained because of
this problem; we are not speaking of a potential security breach here,
but of real sensitive data that have been compromised.
Sure, if Debian is not willing to fix the system, we'll go and fix
our boxen ourselves. But for installing new machines, we will have no
choice but to evict it from our list of possible operating environments
whenever any level of reasonable security is a requirement.