All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fuchs, Andreas <andreas.fuchs at sit.fraunhofer.de>
To: tpm2@lists.01.org
Subject: [tpm2] Re: some questions about Identity
Date: Thu, 09 Jan 2020 09:28:38 +0000	[thread overview]
Message-ID: <9F48E1A823B03B4790B7E6E69430724D0163C46FE8@EXCH2010B.sit.fraunhofer.de> (raw)
In-Reply-To: 18a6bd1e-30cb-2ed5-7f3d-f9ab40b8ed46@uvensys.de

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

What you need are an EK-Certificate that identifies the TPM as original (by TPM vendor)
and a Platform Certificate that assigns the TPM to a platform with serial number and stuff.

The former is typically available.
The latter is typically not provided yet; Sorry.

But keep us posted if you get hold of some Platform Certificates.

Cheers,
Andreas
________________________________________
From: Steffen Schwebel [s.schwebel(a)uvensys.de]
Sent: Thursday, January 09, 2020 09:34
To: tpm2
Subject: [tpm2] some questions about Identity

Hello,

Currently I'm helping a company to roll-out tpm2 support for their Linux
Laptops.
These are mainly Dell Laptops and they come with activate TPM and secure
boot.

Everything working nicely so far.
Right now Im looking for a way to confirm that the device is really the
one Dell provided to us.
Im still waiting for an answer on Dell for that but Im assuming it
should be possible to identify any given system by the Key the OEM deployed.

Am I correct in assuming that? What would be the correct way to do that?

I hope I'm asking this questions in the right mailing list.
This is my first message to the group.

Regards,
Steffen

--
Steffen Schwebel
Mail: s.schwebel(a)uvensys.de
uvensys GmbH

Firmensitz und Sitz der Gesellschaft:
uvensys GmbH
Schorbachstraße 11
35510 Butzbach

HRB: AG Friedberg, 7780
USt-Id: DE282879294

Geschäftsführer:
Dr. Thomas Licht, t.licht(a)uvensys.de
Volker Lieder, v.lieder(a)uvensys.de

Mail: info(a)uvensys.de
Internet: www.uvensys.de

Durchwahl: 06033 - 18 19 225
Hotline: 06033 - 18 19 288
Zentrale: 06033 - 18 19 20
Fax: 06033 - 18 19 299
==========================================================

Jegliche Stellungnahmen und Meinungen dieser E-Mail sind
alleine die des Autors und nicht notwendigerweise die der
Firma. Falls erforderlich, können Sie eine gesonderte
schriftliche Bestätigung anfordern.

Any views or opinions presented in this email are solely
those of the author and do not necessarily represent those
of the company. If verification is required please request
a hard-copy version.

_______________________________________________
tpm2 mailing list -- tpm2(a)lists.01.org
To unsubscribe send an email to tpm2-leave(a)lists.01.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

             reply	other threads:[~2020-01-09  9:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  9:28 Fuchs, Andreas [this message]
2020-01-09 18:43 [tpm2] Re: some questions about Identity Niklas Andersson
2020-01-14 16:00 Steffen
2020-01-15  8:36 Steffen
2020-01-15 14:34 Roberts, William C
2020-01-15 17:17 nicolasoliver03
2020-01-15 18:18 Roberts, William C
2020-01-15 19:33 Desai, Imran
2020-01-15 20:53 Roberts, William C
2020-01-15 22:22 Desai, Imran
2020-01-16 11:34 s.schwebel
2020-01-16 18:42 nicolasoliver03
2020-01-16 22:31 Roberts, William C
2020-01-17  8:29 s.schwebel

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=9F48E1A823B03B4790B7E6E69430724D0163C46FE8@EXCH2010B.sit.fraunhofer.de \
    --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 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.