From Fedora Project Wiki

< Features

Revision as of 22:31, 21 July 2009 by Eparis (talk | contribs) (Created page with '{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To rea...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.


Feature Name

Trusted Boot

Summary

Ability for users to configure their system to make use of the TPM and hardware support in order to verify that the machine is running the intended kernel.

Owner

  • email: eparis@redhat.com

Current status

Detailed Description

Most of the support for trusted boot already exists in Fedora but all of the pieces have never been put together. The goal of this feature is to allow users to boot a kernel, and after it is booted to know that the kernel they are running is the kernel they expected to have running.

Benefit to Fedora

Security minded users have no way of knowing if their kernel is the expected kernel. They have no way of knowing if the system under them has been trojaned. The point of this feature is to give users a method to verify that the system that booted was the system they expected to boot.

Scope

Changes are expected to be needed in grub, tpmutils, trousers, and possibly in the kernel configuration.

How To Test

At the moment testing isn't well defined. Ultimately tests will involve users with TPM enabled hardware to be able to verify the same kernel booted they expected or a different kernel booted than they expected.

User Experience

Noone will notice a change unless they specifically configure their system. There are no planned default changes.

Dependencies

The grub changes, and possibly the intel TXT support are requirements which I may not be able to control but which may cause the feature to fail to complete.

Contingency Plan

None necessary, if it doesn't work, it wasn't going to be default anyway. Users just won't be able to use it.

Documentation

  • Nothing et.

Release Notes

  • No good note yet as there is no documentation. There is no upstream.

Comments and Discussion