From: David Howells <dhowells@redhat.com>
To: rusty@rustcorp.com.au
Cc: keyrings@linux-nfs.org, jwboyer@redhat.com,
linux-kernel@vger.kernel.org, dhowells@redhat.com,
linux-security-module@vger.kernel.org, pjones@redhat.com,
vgoyal@redhat.com
Subject: [RFC][PATCH 00/13] MODSIGN: Use PKCS#7 for module signatures
Date: Mon, 08 Sep 2014 16:37:05 +0100 [thread overview]
Message-ID: <20140908153704.28301.41578.stgit@warthog.procyon.org.uk> (raw)
Here's a set of patches that does the following:
(1) Improves asymmetric keys identification.
Keys derived from X.509 certs now get labelled with IDs derived from their
issuer and certificate number (required to match PKCS#7) and from their
SKID and subject (required to match X.509).
IDs are now binary and match criterion preparsing is provided so that
criteria can be turned into binary blobs to make matching faster.
(2) Improves PKCS#7 message handling to permit PKCS#7 messages without X.509
cert lists to be matched to trusted keys, thereby allowing minimally sized
PKCS#7 certs to be used.
(3) Improves PKCS#7 message handling to better handle certificate chains that
are broken due to unsupported crypto that can otherwise by used to
intersect a trust keyring.
(4) Makes use of the PKCS#7 facility to provide module signatures.
sign-file is replaced with a program that generates a PKCS#7 message that
has no X.509 certs embedded and that has detached data (the module
content) and adds it onto the message with magic string and descriptor.
(5) The PKCS#7 message (and matching X.509 cert) supply all the information
that is needed to select the X.509 cert to be used to verify the signature
by standard means (including selection of digest algorithm and public key
algorithm). No kernel-specific magic values are required.
The following need to be considered also:
(1) How to support externally generated signatures (sign-file -s). Ideally,
externally generated signatures would be provided as PKCS#7 certificates.
(2) How to handle the old signature format: do we change the magic number and
just pretend they don't exist (which would allow us to get rid of most of
the descriptor), do we give an error (which I've chosen to do) or do we
have to support them still?
(3) Do I really need to make one of the X.509-derived IDs out of the subjKeyId
and the subject, or can I just use the subjKeyId by itself? (And likewise
for auth + issuer)
They can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=modsign-pkcs7
David
---
David Howells (13):
Provide a binary to hex conversion utility
KEYS: Preparse match data
KEYS: Remove key_type::def_lookup_type
KEYS: Remove key_type::match in favour of overriding default by match_preparse
KEYS: Make the key matching functions return bool
KEYS: Implement binary asymmetric key ID handling
PKCS#7: Clean up the signed info freeing and fix the parser cleanup
KEYS: Overhaul key identification when searching for asymmetric keys
PKCS#7: Better handling of unsupported crypto
PKCS#7: Handle PKCS#7 messages that contain no X.509 certs
PKCS#7: Allow detached data to be supplied for signature checking purposes
MODSIGN: Provide a utility to append a PKCS#7 signature to a module
MODSIGN: Use PKCS#7 messages as module signatures
crypto/asymmetric_keys/asymmetric_keys.h | 8 -
crypto/asymmetric_keys/asymmetric_type.c | 213 ++++++++++-----
crypto/asymmetric_keys/pkcs7_key_type.c | 2
crypto/asymmetric_keys/pkcs7_parser.c | 66 +++--
crypto/asymmetric_keys/pkcs7_parser.h | 7
crypto/asymmetric_keys/pkcs7_trust.c | 72 +++--
crypto/asymmetric_keys/pkcs7_verify.c | 131 +++++++--
crypto/asymmetric_keys/x509_cert_parser.c | 55 ++--
crypto/asymmetric_keys/x509_parser.h | 6
crypto/asymmetric_keys/x509_public_key.c | 102 ++++---
fs/cifs/cifs_spnego.c | 1
fs/cifs/cifsacl.c | 1
fs/nfs/idmap.c | 2
include/crypto/pkcs7.h | 3
include/crypto/public_key.h | 6
include/keys/asymmetric-type.h | 38 +++
include/keys/user-type.h | 1
include/linux/kernel.h | 1
include/linux/key-type.h | 34 ++
init/Kconfig | 1
kernel/module_signing.c | 220 +++------------
lib/hexdump.c | 18 +
net/dns_resolver/dns_key.c | 18 +
net/rxrpc/ar-key.c | 2
scripts/Makefile | 2
scripts/sign-file | 421 -----------------------------
scripts/sign-file.c | 189 +++++++++++++
security/keys/big_key.c | 2
security/keys/encrypted-keys/encrypted.c | 1
security/keys/internal.h | 10 -
security/keys/key.c | 2
security/keys/keyring.c | 59 +++-
security/keys/proc.c | 8 -
security/keys/process_keys.c | 13 -
security/keys/request_key.c | 21 +
security/keys/request_key_auth.c | 6
security/keys/trusted.c | 1
security/keys/user_defined.c | 14 -
38 files changed, 869 insertions(+), 888 deletions(-)
delete mode 100755 scripts/sign-file
create mode 100755 scripts/sign-file.c
next reply other threads:[~2014-09-08 15:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 15:37 David Howells [this message]
2014-09-08 15:37 ` [PATCH 01/13] Provide a binary to hex conversion utility David Howells
2014-09-08 15:37 ` [PATCH 02/13] KEYS: Preparse match data David Howells
2014-09-08 15:37 ` [PATCH 03/13] KEYS: Remove key_type::def_lookup_type David Howells
2014-09-08 15:37 ` [PATCH 04/13] KEYS: Remove key_type::match in favour of overriding default by match_preparse David Howells
2014-09-08 15:37 ` [PATCH 05/13] KEYS: Make the key matching functions return bool David Howells
2014-09-08 15:38 ` [PATCH 06/13] KEYS: Implement binary asymmetric key ID handling David Howells
2014-09-08 15:38 ` [PATCH 07/13] PKCS#7: Clean up the signed info freeing and fix the parser cleanup David Howells
2014-09-08 15:38 ` [PATCH 08/13] KEYS: Overhaul key identification when searching for asymmetric keys David Howells
2014-10-02 15:49 ` Dmitry Kasatkin
2014-10-02 16:04 ` Dmitry Kasatkin
2014-10-02 18:32 ` Dmitry Kasatkin
2014-10-02 18:38 ` Mimi Zohar
2014-10-03 12:20 ` David Howells
2014-10-03 12:22 ` David Howells
2014-10-03 12:13 ` David Howells
2014-10-03 12:25 ` Dmitry Kasatkin
2014-10-03 12:12 ` David Howells
2014-10-03 12:23 ` Dmitry Kasatkin
2014-09-08 15:38 ` [PATCH 09/13] PKCS#7: Better handling of unsupported crypto David Howells
2014-09-08 15:38 ` [PATCH 10/13] PKCS#7: Handle PKCS#7 messages that contain no X.509 certs David Howells
2014-09-08 15:39 ` [PATCH 11/13] PKCS#7: Allow detached data to be supplied for signature checking purposes David Howells
2014-09-08 15:39 ` [PATCH 12/13] MODSIGN: Provide a utility to append a PKCS#7 signature to a module David Howells
2014-09-08 15:39 ` [PATCH 13/13] MODSIGN: Use PKCS#7 messages as module signatures 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=20140908153704.28301.41578.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jwboyer@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=vgoyal@redhat.com \
/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
all inboxes | Powered by JetHome®