From: Robbie Harwood <rharwood@redhat.com>
To: keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>
Cc: Robbie Harwood <rharwood@redhat.com>
Subject: [PATCH v1 0/2] Fix kexec of pesigned images
Date: Fri, 17 Feb 2023 15:14:33 -0500 [thread overview]
Message-ID: <20230217201435.39784-1-rharwood@redhat.com> (raw)
Hello,
In order to comply with the PE specification, recent versions of pesign do not
include 8-byte padding in the dwLength field. kexec of signed images has
therefore not worked in Fedora (which uses pesign) for some time.
The first commit relaxes the check in order to fix this issue. The second
upgrades several pe_debug() messages to pe_info() in order to make this more
debuggable on systems with secureboot lockdown in place.
Be well,
--Robbie
Robbie Harwood (2):
verify_pefile: relax wrapper length check
asymmetric_keys: log on fatal failures in PE/pkcs7
crypto/asymmetric_keys/pkcs7_verify.c | 10 ++++----
crypto/asymmetric_keys/verify_pefile.c | 32 +++++++++++++++-----------
2 files changed, 23 insertions(+), 19 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-17 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 20:14 Robbie Harwood [this message]
2023-02-17 20:14 ` [PATCH v1 1/2] verify_pefile: relax wrapper length check Robbie Harwood
2023-02-17 21:11 ` Jarkko Sakkinen
2023-02-17 20:14 ` [PATCH v1 2/2] asymmetric_keys: log on fatal failures in PE/pkcs7 Robbie Harwood
2023-02-17 21:14 ` Jarkko Sakkinen
2023-02-17 20:36 ` [PATCH v1 1/2] verify_pefile: relax wrapper length check David Howells
2023-02-17 20:37 ` [PATCH v1 2/2] asymmetric_keys: log on fatal failures in PE/pkcs7 David Howells
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-all 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=20230217201435.39784-1-rharwood@redhat.com \
--to=rharwood@redhat.com \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.