From: Eric Biggers <ebiggers@kernel.org>
To: keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH v2 0/4] KEYS: x509: various cleanups
Date: Tue, 18 Jan 2022 16:54:32 -0800 [thread overview]
Message-ID: <20220119005436.119072-1-ebiggers@kernel.org> (raw)
This series cleans up a few things in the X.509 certificate parser.
Changed v1 => v2:
- Renamed label in patch 3
- Added Acked-by's
Eric Biggers (4):
KEYS: x509: clearly distinguish between key and signature algorithms
KEYS: x509: remove unused fields
KEYS: x509: remove never-set ->unsupported_key flag
KEYS: x509: remove dead code that set ->unsupported_sig
crypto/asymmetric_keys/pkcs7_verify.c | 7 ++---
crypto/asymmetric_keys/x509.asn1 | 2 +-
crypto/asymmetric_keys/x509_cert_parser.c | 34 ++++++++++++-----------
crypto/asymmetric_keys/x509_parser.h | 1 -
crypto/asymmetric_keys/x509_public_key.c | 18 ------------
5 files changed, 21 insertions(+), 41 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-19 0:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 0:54 Eric Biggers [this message]
2022-01-19 0:54 ` [PATCH v2 1/4] KEYS: x509: clearly distinguish between key and signature algorithms Eric Biggers
2022-01-26 14:16 ` Jarkko Sakkinen
2022-01-19 0:54 ` [PATCH v2 2/4] KEYS: x509: remove unused fields Eric Biggers
2022-01-26 14:14 ` Jarkko Sakkinen
2022-01-19 0:54 ` [PATCH v2 3/4] KEYS: x509: remove never-set ->unsupported_key flag Eric Biggers
2022-01-26 14:13 ` Jarkko Sakkinen
2022-01-19 0:54 ` [PATCH v2 4/4] KEYS: x509: remove dead code that set ->unsupported_sig Eric Biggers
2022-01-26 14:14 ` Jarkko Sakkinen
2022-01-26 14:16 ` [PATCH v2 0/4] KEYS: x509: various cleanups Jarkko Sakkinen
2022-01-26 14:19 ` Jarkko Sakkinen
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=20220119005436.119072-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@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.