TPM2 (Trusted Platform Module) userspace development
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm at redhat.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] Issue Solved/Trusted Boot
Date: Mon, 04 Sep 2017 12:04:46 +0200	[thread overview]
Message-ID: <a15fb54a-9d7c-657f-13f4-2c03435d8e5b@redhat.com> (raw)
In-Reply-To: CAHM15e3xAx4wz+t_X4-SJO9N2JVqF7KHbuFASdJJHjYr2TbaEg@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

Hello Haydon,

On 09/04/2017 11:27 AM, Haydon Cardew wrote:
> Hi,
> 
> 
> 
> Following a discussion on 01org/tpm2-tools #444 [https://github.com/01org/
> tpm2-tools/issues/444] I wanted to post an update on what the issue was.
>

I'm glad that your issue got solved.
 > 
> If I could ask one further thing (I believe this is the correct place to
> post this?), I’m looking at setting up a trusted boot system on my current
> setup (Ubuntu 16.04, kernel 4.4) to be used with the now working tpm2. I
> have previously done this with tpm1.2 but the process seems rather
> different this time, if anyone can point me to any good resources/tutorials
> that would be a massive help.
> 

There isn't a single way to do this, so it depends on what kind of system you
want to use and what is your threat model.

For example, do you want to boot your system in EFI or BIOS mode? do you want
to use Secure Boot or no?

For me the best way to do this is to use UEFI + Secure Boot and to seal your
secrets against PCR7 as described in this blog post [0] from Matthew Garret.

But for that you need latest shim that measures certificates into PCR7 [1] and
TPM2 measurement support in grub2 [2] that haven't landed yet.

If you want to boot your system in BIOS mode, then you have other options like
the TrustedGrub2 project [3].

[0]: https://mjg59.dreamwidth.org/48897.html
[1]: https://github.com/rhboot/shim/commit/8af7c4cacaf753f38f2564b26b962a7a2942d664
[2]: http://lists.gnu.org/archive/html/grub-devel/2017-07/msg00003.html
[3]: https://github.com/Rohde-Schwarz-Cybersecurity/TrustedGRUB2

Best regards,
-- 
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat

             reply	other threads:[~2017-09-04 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 10:04 Javier Martinez Canillas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-11 16:08 [tpm2] Issue Solved/Trusted Boot Haydon Cardew
2017-09-06 19:28 Javier Martinez Canillas
2017-09-06 16:16 Philip Tricca
2017-09-04  9:27 Haydon Cardew

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=a15fb54a-9d7c-657f-13f4-2c03435d8e5b@redhat.com \
    --to=tpm2@lists.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox