From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] KEYS: Miscellaneous fixes
Date: Tue, 26 Jun 2018 16:59:27 +0100 [thread overview]
Message-ID: <153002876741.31726.8580751276453556884.stgit@warthog.procyon.org.uk> (raw)
Hi James,
Here's a bunch of miscellaneous fixes:
(1) Fix the handling of the X.509 signature BIT STRING.
(2) Fix a section declaration.
(3) Fix rounding in KDF.
Could you pass these on to Linus please?
The patches can be found here tagged thusly:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
keys-fixes-20180626
and also on the following branch:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-fixes
David
---
Eric Biggers (1):
dh key: fix rounding up KDF output length
Maciej S. Szmigiero (1):
X.509: unpack RSA signatureValue field from BIT STRING
Nick Desaulniers (1):
certs/blacklist: fix const confusion
certs/blacklist.h | 2 +-
crypto/asymmetric_keys/x509_cert_parser.c | 9 +++++++++
security/keys/dh.c | 6 ++++--
3 files changed, 14 insertions(+), 3 deletions(-)
next reply other threads:[~2018-06-26 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 15:59 David Howells [this message]
2018-06-26 15:59 ` [PATCH 1/3] X.509: unpack RSA signatureValue field from BIT STRING David Howells
2018-06-26 15:59 ` [PATCH 2/3] certs/blacklist: fix const confusion David Howells
2018-06-26 15:59 ` [PATCH 3/3] dh key: fix rounding up KDF output length David Howells
2018-06-26 16:39 ` [PATCH 0/3] KEYS: Miscellaneous fixes James Morris
-- strict thread matches above, loose matches on Subject: below --
2016-07-17 23:10 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=153002876741.31726.8580751276453556884.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).