public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Liming Gao <liming.gao@intel.com>
To: edk2-devel@lists.01.org
Subject: [Patch 0/2] MdeModulePkg PeiCore: Signed GUIDED section may not be dispatched
Date: Thu,  9 Feb 2017 12:14:50 +0800	[thread overview]
Message-ID: <1486613692-11076-1-git-send-email-liming.gao@intel.com> (raw)

https://bugzilla.tianocore.org/show_bug.cgi?id=365

When RSA2048 GUIDED section has SIGNED attribute only without PROCESSED_REQUIRED 
attribute, it will not be processed correctly once RSA2048 GUIDED extraction 
service is dispatcher later, because PeiCore cache GUIDED section with 
EFI_AUTH_STATUS_NOT_TESTED.

Here is the failure case. RSA Extraction Service is compressed. DxeIpl installs
the decompress service. On the first round dispatcher, FVMAIN is cached with 
EFI_AUTH_STATUS_NOT_TESTED. It can't be dispatched again. 

INF RuleOverride = LzmaCompress MdeModulePkg/../SectionExtractionPei.inf
FILE FV_IMAGE = 9E21FD93-9C72-4c15-8C4B-E77F1DB2D792 {
  SECTION GUIDED A7717414-C616-4977-9420-844712A735BF AUTH_STATUS_VALID = TRUE
    SECTION FV_IMAGE = FVMAIN
  }
}
INF  MdeModulePkg/Core/DxeIplPeim/DxeIpl.inf

Liming Gao (2):
  MdeModulePkg PeiCore: Reset PeimNeedingDispatch when its security
    violation
  MdeModulePkg PeiCore: Don't cache GUIDED section with AUTH_NOT_TESTED

 MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c |  9 ++++++++-
 MdeModulePkg/Core/Pei/FwVol/FwVol.c           | 24 +++++++++++++-----------
 2 files changed, 21 insertions(+), 12 deletions(-)

-- 
2.8.0.windows.1



             reply	other threads:[~2017-02-09  4:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  4:14 Liming Gao [this message]
2017-02-09  4:14 ` [Patch 1/2] MdeModulePkg PeiCore: Reset PeimNeedingDispatch when its security violation Liming Gao
2017-02-09  4:44   ` Zeng, Star
2017-02-09  4:14 ` [Patch 2/2] MdeModulePkg PeiCore: Don't cache GUIDED section with AUTH_NOT_TESTED Liming Gao
2017-02-09  4:40   ` Zeng, Star

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=1486613692-11076-1-git-send-email-liming.gao@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