public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Stefan Berger" <stefanb@linux.ibm.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: "mhaeuser@posteo.de" <mhaeuser@posteo.de>,
	"spbrogan@outlook.com" <spbrogan@outlook.com>,
	"marcandre.lureau@redhat.com" <marcandre.lureau@redhat.com>,
	"kraxel@redhat.com" <kraxel@redhat.com>
Subject: Re: [edk2-devel] [PATCH v5 0/8] Ovmf: Disable the TPM2 platform hierarchy
Date: Wed, 8 Sep 2021 16:34:48 -0400	[thread overview]
Message-ID: <7eb6e6d2-2e1d-850b-50bd-d0c466662f38@linux.ibm.com> (raw)
In-Reply-To: <PH0PR11MB4885AC097CD2D8182469EE728CD49@PH0PR11MB4885.namprd11.prod.outlook.com>


On 9/8/21 10:37 AM, Yao, Jiewen wrote:
> Hi Stefan
> According to our security policy, the PPI must be sent before EndOfDxe.
> Then registering PlatformAuth clear at EndOfDxe is safe. I still don’t get your point on why we have do in PlatformBds.
>
> At least, I do want to make sure all X86 implementation are align to one solution.
>
> Also, for PEI, I don’t think we shall modify the Tcg2Pei in this patch set.
> The platform auth clear is platform action. I think we need a standalone PEIM, to allow platform do its own stuff.
>
> All in all, I try to understand, why not just copy the solution in MinPlatformPkg?
> A standalone TcgPlatformPei/Dxe?

I tried to import Tcg2PlatformDxe with it's .c and .inf files but cannot 
get its EntryPoint invoked when running OvmfPkg/OvmfPkgX64.dsc


>
> Thank you
> Yao Jiewen
>

  reply	other threads:[~2021-09-08 20:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 21:21 [PATCH v5 0/8] Ovmf: Disable the TPM2 platform hierarchy Stefan Berger
2021-09-01 21:21 ` [PATCH v5 1/8] SecurityPkg/TPM: Import PeiDxeTpmPlatformHierarchyLib.c from edk2-platforms Stefan Berger
2021-09-01 21:21 ` [PATCH v5 2/8] SecurityPkg/TPM: Fix bugs in imported PeiDxeTpmPlatformHierarchyLib Stefan Berger
2021-09-01 21:21 ` [PATCH v5 3/8] SecurityPkg/TPM: Add a NULL implementation of TpmPlatformHierarchyLib Stefan Berger
2021-09-01 21:21 ` [PATCH v5 4/8] SecurityPkg: Introduce new PCD PcdRandomizePlatformHierarchy Stefan Berger
2021-09-01 21:21 ` [PATCH v5 5/8] OvmfPkg: Reference new TPM classes in the build system for compilation Stefan Berger
2021-09-01 21:21 ` [PATCH v5 6/8] OvmfPkg: Disable the TPM2 platform hierarchy Stefan Berger
2021-09-01 21:21 ` [PATCH v5 7/8] ArmVirtPkg: Reference new TPM classes in the build system for compilation Stefan Berger
2021-09-01 21:21 ` [PATCH v5 8/8] ArmVirtPkg: Disable the TPM2 platform hierarchy Stefan Berger
2021-09-02  1:27 ` [edk2-devel] [PATCH v5 0/8] Ovmf: " Stefan Berger
2021-09-06 12:34 ` Yao, Jiewen
2021-09-06 13:50   ` [edk2-devel] " Stefan Berger
2021-09-06 15:05     ` Yao, Jiewen
     [not found]     ` <16A243F1DBDE42C8.5578@groups.io>
2021-09-06 15:07       ` Yao, Jiewen
2021-09-07 19:41         ` Stefan Berger
2021-09-07 19:44         ` Stefan Berger
2021-09-08 12:53   ` Stefan Berger
2021-09-08 14:37     ` Yao, Jiewen
2021-09-08 20:34       ` Stefan Berger [this message]
2021-09-09  0:19         ` Yao, Jiewen
2021-09-09 11:13           ` Stefan Berger
2021-09-09 11:37             ` Gerd Hoffmann
2021-09-09 16:15               ` Stefan Berger

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-list 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=7eb6e6d2-2e1d-850b-50bd-d0c466662f38@linux.ibm.com \
    --to=devel@edk2.groups.io \
    /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