Security: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Updated most wanted security features) |
||
| Line 2: | Line 2: | ||
<div style="color:red">This page is work in progress!</div> | <div style="color:red">This page is work in progress!</div> | ||
== Common security features == | |||
* Boot password (like BIOS password) | |||
* RAM wiping after each boot | |||
* Signature verification - to boot from payload only signing images | |||
* Support to encrypted block devices/volumes | |||
== RAM wiping == | == RAM wiping == | ||
Revision as of 15:11, 15 May 2010
This page explains how coreboot can help with various security aspects of your system, compared to closed-source, legacy BIOS/EFI/firmware implementations.
This page is work in progress!
Common security features
- Boot password (like BIOS password)
- RAM wiping after each boot
- Signature verification - to boot from payload only signing images
- Support to encrypted block devices/volumes
RAM wiping
- http://citp.princeton.edu/memory/
- Coreinfo as demo payload for coreboot, showing your RAM contents after a cold boot.
SMI issues
- http://www.ssi.gouv.fr/fr/sciences/fichiers/lti/cansecwest2006-duflot.pdf
- http://tracker.coreboot.org/trac/coreboot/ticket/42
ATA issues
- http://coreboot.org/pipermail/coreboot/2005-May/011686.html
- http://www.heise.de/ct/english/05/08/172/
BIOS password feature
- Bayou / coreinfo based "BIOS password" feature, using SHA-1 hashes stored in NVRAM or the (flash) ROM chip.
Firewire issues
- http://md.hudora.de/presentations/firewire/
- http://www.hermann-uwe.de/blog/physical-memory-attacks-via-firewire-dma-part-1-overview-and-mitigation