From: Dmitry Kasatkin <d.kasatkin@samsung.com>
To: zohar@linux.vnet.ibm.com, dhowells@redhat.com,
jwboyer@redhat.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Dmitry Kasatkin <d.kasatkin@samsung.com>
Subject: [PATCH v2 0/3] KEYS: validate certificate trust with selected owner or builtin key
Date: Tue, 17 Jun 2014 11:56:56 +0300 [thread overview]
Message-ID: <cover.1402994752.git.d.kasatkin@samsung.com> (raw)
Instead of allowing public keys, with certificates signed by any key on
the system trusted keyring, to be added to a trusted keyring, this patch
set further restricts the certificates to those signed by a particular key
or builtin keys on the system keyring.
This patch defines a new kernel parameter 'keys_ownerid={id: | builtin}'
to use specific key or any builtin key.
Changes to v1:
* key id matching code from asymmetric_type.c is reused in the patch
Thanks,
Dmitry
Dmitry Kasatkin (3):
KEYS: make key id matching as a dedicated function
KEYS: validate certificate trust only with selected owner key
KEYS: validate certificate trust only with builtin keys
Documentation/kernel-parameters.txt | 5 ++++
crypto/asymmetric_keys/asymmetric_keys.h | 2 ++
crypto/asymmetric_keys/asymmetric_type.c | 50 ++++++++++++++++++++------------
crypto/asymmetric_keys/x509_public_key.c | 26 +++++++++++++++--
include/linux/key.h | 1 +
kernel/system_keyring.c | 1 +
6 files changed, 64 insertions(+), 21 deletions(-)
--
1.9.1
next reply other threads:[~2014-06-17 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 8:56 Dmitry Kasatkin [this message]
2014-06-17 8:56 ` [PATCH v2 1/3] KEYS: make key id matching as a dedicated function Dmitry Kasatkin
2014-06-18 1:07 ` Mimi Zohar
2014-06-17 8:56 ` [PATCH v2 2/3] KEYS: validate certificate trust only with selected owner key Dmitry Kasatkin
2014-06-17 8:56 ` [PATCH v2 3/3] KEYS: validate certificate trust only with builtin keys Dmitry Kasatkin
2014-06-17 12:20 ` [PATCH v2 0/3] KEYS: validate certificate trust with selected owner or builtin key Mimi Zohar
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.1402994752.git.d.kasatkin@samsung.com \
--to=d.kasatkin@samsung.com \
--cc=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=zohar@linux.vnet.ibm.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