[121945] in cryptography@c2.net mail archive
Re: Just update the microcode (was: Re: defending against evil in
daemon@ATHENA.MIT.EDU (alex@alten.org)
Tue Apr 29 11:25:35 2008
From: alex@alten.org
To: "John Ioannidis" <ji@tla.org>
Cc: Cryptography <cryptography@metzdowd.com>,
"Leichter, Jerry"
<leichter_jerrold@emc.com>,
"John Denker"
<jsd@av8n.com>,
"Scott Guthery"
<sbg@acw.com>,
"Ed Gerck"
<edgerck@nma.com>
Date: Mon, 28 Apr 2008 21:12:14 -0700
No need to be a major power. Linux patches x86 code, as does Windows. I r=
an across a project several years ago that modified the microcode for some =
i/o x86 assembly instructions. Here's a good link explaining it all.=20=20
http://en.wikipedia.org/wiki/Microcode
All this hw/sw flexibility makes designing a good security system a real ch=
allenge. You need a reference monitor somewhere in it that you can truly t=
rust.
- Alex
> ----- Original Message -----
> From: "John Ioannidis" <ji@tla.org>
> To: Cryptography <cryptography@metzdowd.com>
> Subject: Just update the microcode (was: Re: defending against=20
> evil in all layers of hardware and software)
> Date: Mon, 28 Apr 2008 18:16:12 -0400
>=20
>=20
> Intel and AMD processors can have new microcode loaded to them, and=20
> this is usually done by the BIOS. Presumably there is some=20
> asymmetric crypto involved with the processor doing the signature=20
> validation.
>=20
> A major power that makes a good fraction of the world's laptops and=20
> desktops (and hence controls the circuitry and the BIOS, even if=20
> they do not control the chip manufacturing process) would be in a=20
> good place to introduce problems that way, no?
>=20
> /ji
>=20
> ---------------------------------------------------------------------
> The Cryptography Mailing List
> Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.c=
om
>=20
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com
