From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org, Daniel Kiper <daniel.kiper@oracle.com>
Cc: Glenn Washburn <development@efficientek.com>
Subject: [PATCH 0/4] Various LUKS2 improvements
Date: Fri, 19 Mar 2021 19:14:47 -0500 [thread overview]
Message-ID: <cover.1616198999.git.development@efficientek.com> (raw)
Patch #1: Allows GRUB to be more resilient in the fact or unexpected json
data, thus allowing access to LUKS2 volumes in cases where currently it
would be inaccessible
Patch #2-3: Add some text to go along with the error in case it gets
bubbled up to the user
Patch #4: Simplifies some error handling and makes the code a little easier
to read
Glenn
Glenn Washburn (4):
luks2: Continue trying all keyslots even if there are some failures
luks2: Add error message strings to crypto errors
luks2: Add error message strings to errors in luks2_read_header
luks2: Fix potential grub_free with NULL pointer
grub-core/disk/luks2.c | 58 ++++++++++++++++++++----------------------
1 file changed, 28 insertions(+), 30 deletions(-)
--
2.27.0
next reply other threads:[~2021-03-20 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 0:14 Glenn Washburn [this message]
2021-03-20 0:14 ` [PATCH 1/4] luks2: Continue trying all keyslots even if there are some failures Glenn Washburn
2021-03-20 0:14 ` [PATCH 2/4] luks2: Add error message strings to crypto errors Glenn Washburn
2021-03-20 0:14 ` [PATCH 3/4] luks2: Add error message strings to errors in luks2_read_header Glenn Washburn
2021-03-20 0:14 ` [PATCH 4/4] luks2: Fix potential grub_free with NULL pointer Glenn Washburn
2021-03-23 17:43 ` [PATCH 0/4] Various LUKS2 improvements Daniel Kiper
2021-03-23 19:41 ` Daniel Kiper
2021-03-24 4:01 ` Glenn Washburn
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=cover.1616198999.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=daniel.kiper@oracle.com \
--cc=grub-devel@gnu.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.