From: "Nhi Pham" <nhi@os.amperecomputing.com>
To: "Xu, Min M" <min.m.xu@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"nhi@os.amperecomputing.com" <nhi@os.amperecomputing.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>
Cc: "patches@amperecomputing.com" <patches@amperecomputing.com>
Subject: Re: [edk2-devel] [PATCH 1/1] SecurityPkg/DxeImageVerificationLib: Add AUTH_SIG_NOT_FOUND Action
Date: Thu, 20 Apr 2023 10:48:55 +0700 [thread overview]
Message-ID: <b899b0e9-4636-8070-5a78-7aff2ecd3ca2@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <PH0PR11MB50649579CDA7B848980273F3C59D9@PH0PR11MB5064.namprd11.prod.outlook.com>
Hi Min,
This SEI test passes:
SecureBoot - TestImage2.bin in Image Execution Info Table with
SIG_NOT_FOUND. -- PASS
00C3C2F2-39D5-4D35-B7E7-587CA0F3CB75
SctPkg/TestCase/UEFI/EFI/RuntimeServices/SecureBoot/BlackBoxTest/ImageLoadingBBTest.c:1103:Status
- Success
The test image binary is different to the one in the commit message due
to some bug fixes in the SEI test suite. The right test case to catch
this bug is 00C3C2F2-39D5-4D35-B7E7-587CA0F3CB75
You can check the test code at
https://github.com/ARM-software/bbr-acs/blob/main/bbsr/sct-tests/SecureBoot/BlackBoxTest/ImageLoadingBBTest.c
Thanks,
Nhi
On 4/19/2023 6:20 AM, Xu, Min M wrote:
> On Friday, April 14, 2023 1:18 PM, Nhi Pham wrote:
>> Hi,
>>
>> Ping for reviewing.
>>
>> Let me know if I need anything for this patch.
> Do you test the change and what's the test result? Can you provide the validation result?
>
> Thanks
> Min
next prev parent reply other threads:[~2023-04-20 3:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 9:21 [PATCH 1/1] SecurityPkg/DxeImageVerificationLib: Add AUTH_SIG_NOT_FOUND Action Nhi Pham
2023-04-14 5:18 ` Nhi Pham
2023-04-18 23:20 ` [edk2-devel] " Min Xu
2023-04-20 3:48 ` Nhi Pham [this message]
2023-04-26 7:54 ` Min Xu
2023-04-27 5:38 ` Nhi Pham
2023-04-27 5:46 ` Min Xu
2023-04-27 8:19 ` Yao, Jiewen
2023-04-28 3:14 ` Nhi Pham
2023-04-28 11:08 ` [edk2-devel] " Yao, Jiewen
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=b899b0e9-4636-8070-5a78-7aff2ecd3ca2@amperemail.onmicrosoft.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