From: eddantes@wanadoo.fr
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SSSCA: We're in trouble now
Date: Sat, 02 Mar 2002 04:03:14 +0100 [thread overview]
Message-ID: <3C8040F2.9060208@wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.05.10203021402030.4035-100000@marina.lowendale.com.au>
Neale Banks wrote:
[snip]
> All too true. However, given the quality of BIOS code we have seen
> over the years, the thought of your average BIOS programmer
> implementing cryptographic techniques does provide some amusement
> ;-)
PnP crypto? I'd love to see it. :)
That could actually be used somehow as some sort of pseudo-random
generator, given the legendary oh-so-predictable behaviour of most
BIOSes, even in normal circumstances... :D
> Any chance of any manafacturers open-sourcing their BIOS?
Uhmm... Odds: 1 in <buffer overflow>
Considering that they seem to see BIOSes as the easiest way to hide
hardware design mistakes, they probably wont.
OTOH, why not sticking Linux straight into BIOS flash chips?
Have a look here (sorry if you already knew):
http://www.linuxbios.org/
http://freebios.sourceforge.net/
Or just implement an OpenFirmware BIOS (that's cool! :)?
http://www.freiburg.linux.de/openbios/
> Regards, Neale.
All hope is not lost! ;)
Have fun.
/Dantes
next prev parent reply other threads:[~2002-03-02 3:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 19:46 SSSCA: We're in trouble now Paul G. Allen
2002-03-01 20:27 ` Shawn Starr
2002-03-01 20:30 ` Xavier Bestel
2002-03-01 21:29 ` Shawn Starr
2002-03-01 22:19 ` Alan Cox
2002-03-02 3:08 ` Neale Banks
2002-03-02 3:03 ` eddantes [this message]
2002-03-02 18:32 ` Alan Cox
2002-03-01 22:47 ` Florian Weimer
2002-03-02 2:59 ` Paul G. Allen
2002-03-06 4:26 ` Petro
2002-03-06 4:41 ` Trever L. Adams
2002-03-06 16:26 ` Rik van Riel
2002-03-06 17:03 ` Richard B. Johnson
2002-03-06 18:16 ` Paul G. Allen
2002-03-06 18:35 ` Trever L. Adams
2002-03-07 22:54 ` Florian Weimer
2002-03-08 2:12 ` Tom Rauschenbach
-- strict thread matches above, loose matches on Subject: below --
2002-03-02 0:21 Thomas Hood
2002-03-02 8:35 ` Florian Weimer
2002-03-02 17:34 ` M. Edward (Ed) Borasky
2002-03-04 8:30 ` Helge Hafting
2002-03-04 9:40 ` Martin Eriksson
2002-03-04 17:02 ` Paul G. Allen
2002-03-06 4:41 ` Petro
2002-03-06 9:27 ` Helge Hafting
2002-03-02 15:30 ` Paul P Komkoff Jr
2002-03-02 21:58 ` Rik van Riel
2002-03-03 1:29 ` Greg Louis
2002-03-06 4:51 ` Petro
2002-03-02 17:47 ` Jurgen Botz
2002-03-06 5:00 ` Petro
2002-03-06 16:42 ` Alan Cox
2002-03-06 18:24 ` Paul G. Allen
2002-03-06 23:56 ` Petro
2002-03-04 19:27 Jesse Pollard
2002-03-06 17:20 Ed Vance
2002-03-06 18:31 ` Paul G. Allen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C8040F2.9060208@wanadoo.fr \
--to=eddantes@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.