Bug#56821: [POSSIBLE GRAVE SECURITY HOLD]
- To: John Goerzen <email@example.com>
- Cc: Pierre Beyssac <firstname.lastname@example.org>, Ruud de Rooij <email@example.com>, 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: Thierry Laronde <email@example.com>
- Date: Wed, 2 Feb 2000 18:03:20 +0100
- Message-id: <20000202180320.A772@polynum.com>
- Reply-to: Thierry Laronde <firstname.lastname@example.org>, email@example.com
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com> <389823E6.37B56639@cupid.suninternet.com> <20000202045337.A10828@debian.org> <firstname.lastname@example.org> <20000202145212.S99806@enst.fr> <email@example.com>
On Wed, Feb 02, 2000 at 09:47:54AM -0600, John Goerzen wrote:
> Pierre Beyssac <firstname.lastname@example.org> writes:
> > You miss the point. That this can be fixed by configuration doesn't
> > mean it's not a security hole in the first place.
> > The security hole is that the console is made insecure by default
> > without any warning from the installation program. That, in itself,
> > would warrant a security advisory.
> The console is automatically insecure. What led you to believe
Specially when, like in slink, the lack of a file /etc/shutdown.allow allows
anybody to reboot...
> > On the other hand, nobody knows that you ALSO have to edit the
> > boot= line in lilo.conf to remove the dangerous MBR.
> Do people also know that you have to padlock your computer's case
> shut? That you have to password-protect the BIOS? That you have to
> password-protect LILO? None of these have an obvious prompt, and on
> some computers may require physical case modifications.
All that you have cited are *NOT* operating system issues. The BIOS is not
Debian, the hardware is not Debian, etc...
What is asked for is, at least, *DOCUMENTATION*.
Let me remind... I have read that somewhere... Perhaps you can tell :
"WE WON'T HIDE PROBLEMS"
website : http://www.polynum.com