From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "heyi.guo@linaro.org" <heyi.guo@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Zhang, Chao B" <chao.b.zhang@intel.com>
Subject: Re: Question about SecurityPkg/DxeTcg2PhysicalPresenceLib
Date: Fri, 10 Aug 2018 09:12:46 +0000 [thread overview]
Message-ID: <67261275-360A-40ED-A668-AF1265A39AFD@intel.com> (raw)
In-Reply-To: <20180810084950.GA32368@ecs-e536.expressvpn>
by design a platform need define a trusted console and only connect this trusted console before endofdxe
thank you!
Yao, Jiewen
> 在 2018年8月10日,下午4:50,"heyi.guo@linaro.org" <heyi.guo@linaro.org> 写道:
>
> Hi folks,
>
> The function Tcg2PhysicalPresenceLibProcessRequest in DxeTcg2PhysicalPresenceLib
> requires to be invoked after console is ready, and in the function it will call
> VariableLockProtocol->RequestToLock(), while variable RequestToLock() requires
> to be called before "End Of Dxe" event, or else it will return ACCESS_DENIED.
>
> However, in PI spec 1.6, section 5.1.2.1 "End of DXE Event", it says "Prior to
> connecting consoles, the platform should signal the event 'End of DXE'". So
> there seems to be contradiction between these implementations and PI spec.
>
> If we follow below work flow:
> End of DXE -> connect console -> Tcg2PhysicalPresenceLibProcessRequest() ->
> Variable RequestToLock() -> we will get ACCESS_DENIED.
>
> Please advise,
>
> Thanks,
>
> Heyi
next prev parent reply other threads:[~2018-08-10 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 8:49 Question about SecurityPkg/DxeTcg2PhysicalPresenceLib heyi.guo
2018-08-10 9:12 ` Yao, Jiewen [this message]
2018-08-13 1:07 ` heyi.guo
2018-08-13 1:10 ` Yao, Jiewen
2018-08-14 6:18 ` heyi.guo
2018-08-14 14:51 ` Laszlo Ersek
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=67261275-360A-40ED-A668-AF1265A39AFD@intel.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