From: Laszlo Ersek <lersek@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Zhang Lubo <lubo.zhang@intel.com>
Subject: Re: [PATCH] SecurityPkg: fix sha256 signature check
Date: Thu, 10 May 2018 14:36:00 +0200 [thread overview]
Message-ID: <1595cae2-f01d-57e2-6c2b-2cbb472d7a84@redhat.com> (raw)
In-Reply-To: <1525903747.5882.11.camel@HansenPartnership.com>
On 05/10/18 00:09, James Bottomley wrote:
> commit c035e37335ae43229d7e68de74a65f2c01ebc0af
> Author: Zhang Lubo <lubo.zhang@intel.com>
> Date: Thu Jan 5 14:58:05 2017 +0800
>
> SecurityPkg: enhance secure boot Config Dxe & Time Based AuthVariable.
>
> Added a check for sha256 being the ownly allowed signature hash.
> Unfortuantely this commit assumed the form of the signature data was a
> raw SignedData sequence. Most tools actually generate a ContentInfo
> sequence instead which contains a header identifying the content as
> pkcs7-SignedData. Fix this check to allow either format to work.
>
> This fix is needed at least for efitools because we generate signed
> variable updates with the ContentInfo header.
>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> ---
> CryptoPkg/Library/OpensslLib/openssl | 2 +-
> SecurityPkg/Library/AuthVariableLib/AuthService.c | 11 ++++++++++-
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/CryptoPkg/Library/OpensslLib/openssl b/CryptoPkg/Library/OpensslLib/openssl
> index b2758a2292..d4e4bd2a81 160000
> --- a/CryptoPkg/Library/OpensslLib/openssl
> +++ b/CryptoPkg/Library/OpensslLib/openssl
> @@ -1 +1 @@
> -Subproject commit b2758a2292aceda93e9f44c219b94fe21bb9a650
> +Subproject commit d4e4bd2a8163f355fa8a3884077eaec7adc75ff7
This hunk should not be necessary; please see edk2 commit b85b20fba42e
("CryptoPkg/OpensslLib: Update OpenSSL version to 1.1.0h", 2018-04-15).
(I'll let the SecurityPkg maintainers review the rest.)
Thanks,
Laszlo
> diff --git a/SecurityPkg/Library/AuthVariableLib/AuthService.c b/SecurityPkg/Library/AuthVariableLib/AuthService.c
> index 213a524f27..855ea3350a 100644
> --- a/SecurityPkg/Library/AuthVariableLib/AuthService.c
> +++ b/SecurityPkg/Library/AuthVariableLib/AuthService.c
> @@ -1908,10 +1908,19 @@ VerifyTimeBasedPayload (
> // in VARIABLE_AUTHENTICATION_2 descriptor.
> // This field has the fixed offset (+13) and be calculated based on two bytes of length encoding.
> //
> + // However the data may also begin
> + // ContentInfo ::= SEQUENCE {
> + // contentType ContentType,
> + // content
> + // [0] EXPLICIT ANY DEFINED BY contentType OPTIONAL }
> + //
> + // In which case the fixed offset is +32
> + //
> if ((Attributes & EFI_VARIABLE_TIME_BASED_AUTHENTICATED_WRITE_ACCESS) != 0) {
> if (SigDataSize >= (13 + sizeof (mSha256OidValue))) {
> if (((*(SigData + 1) & TWO_BYTE_ENCODE) != TWO_BYTE_ENCODE) ||
> - (CompareMem (SigData + 13, &mSha256OidValue, sizeof (mSha256OidValue)) != 0)) {
> + (CompareMem (SigData + 13, &mSha256OidValue, sizeof (mSha256OidValue)) != 0 &&
> + CompareMem (SigData + 32, &mSha256OidValue, sizeof (mSha256OidValue)) != 0)) {
> return EFI_SECURITY_VIOLATION;
> }
> }
>
next prev parent reply other threads:[~2018-05-10 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 22:09 [PATCH] SecurityPkg: fix sha256 signature check James Bottomley
2018-05-10 12:36 ` Laszlo Ersek [this message]
2018-05-11 8:25 ` Long, Qin
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=1595cae2-f01d-57e2-6c2b-2cbb472d7a84@redhat.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