mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: zohar@linux.vnet.ibm.com
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
	keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 08/12] KEYS: Make the system trusted keyring depend on the asymmetric key type [ver #2]
Date: Fri, 04 Mar 2016 15:01:20 +0000	[thread overview]
Message-ID: <20160304150120.17121.33822.stgit@warthog.procyon.org.uk> (raw)
In-Reply-To: <20160304150022.17121.34501.stgit@warthog.procyon.org.uk>

Make the system trusted keyring depend on the asymmetric key type as
there's not a lot of point having it if you can't then load asymmetric keys
onto it.

Signed-off-by: David Howells <dhowells@redhat.com>
---

 certs/Kconfig |    1 +
 1 file changed, 1 insertion(+)

diff --git a/certs/Kconfig b/certs/Kconfig
index f0f8a4433685..743d480f5f6f 100644
--- a/certs/Kconfig
+++ b/certs/Kconfig
@@ -17,6 +17,7 @@ config MODULE_SIG_KEY
 config SYSTEM_TRUSTED_KEYRING
 	bool "Provide system-wide ring of trusted keys"
 	depends on KEYS
+	depends on ASYMMETRIC_KEY_TYPE
 	help
 	  Provide a system keyring to which trusted keys can be added.  Keys in
 	  the keyring are considered to be trusted.  Keys may be added at will

  parent reply	other threads:[~2016-03-04 15:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 15:00 [RFC PATCH 00/12] KEYS: Restrict additions to 'trusted' keyrings " David Howells
2016-03-04 15:00 ` [RFC PATCH 01/12] KEYS: Generalise system_verify_data() to provide access to internal content " David Howells
2016-03-04 15:00 ` [RFC PATCH 02/12] PKCS#7: Make trust determination dependent on contents of trust keyring " David Howells
2016-03-04 15:00 ` [RFC PATCH 03/12] KEYS: Add a facility to restrict new links into a " David Howells
2016-03-04 15:00 ` [RFC PATCH 04/12] KEYS: Move x509_request_asymmetric_key() to asymmetric_type.c " David Howells
2016-03-04 15:00 ` [RFC PATCH 05/12] KEYS: Generalise x509_request_asymmetric_key() " David Howells
2016-03-04 15:01 ` [RFC PATCH 06/12] X.509: Use verify_signature() if we have a struct key * to use " David Howells
2016-03-04 15:01 ` [RFC PATCH 07/12] X.509: Move the trust validation code out to its own file " David Howells
2016-03-04 15:01 ` David Howells [this message]
2016-03-04 15:01 ` [RFC PATCH 09/12] KEYS: Move the point of trust determination to __key_link() " David Howells
2016-03-04 15:01 ` [RFC PATCH 10/12] KEYS: Remove KEY_FLAG_TRUSTED and KEY_ALLOC_TRUSTED " David Howells
2016-03-04 15:01 ` [RFC PATCH 11/12] certs: Add a secondary system keyring that can be added to dynamically " David Howells
2016-03-08  2:05   ` Mimi Zohar
2016-03-08 13:13   ` David Howells
2016-03-08 14:06     ` Petko Manolov
2016-03-08 14:31     ` Mimi Zohar
2016-03-08 14:43     ` David Howells
2016-03-08 15:09       ` Mimi Zohar
2016-03-08 15:32       ` David Howells
2016-03-08 16:15         ` Mimi Zohar
2016-03-04 15:01 ` [RFC PATCH 12/12] IMA: Use the the system trusted keyrings instead of .ima_mok " David Howells
2016-03-08  2:26   ` Mimi Zohar
2016-03-08 13:08   ` David Howells
2016-03-08 14:12     ` Mimi Zohar
2016-03-08 14:14     ` Petko Manolov
2016-03-08 14:38       ` Mimi Zohar
2016-03-08 14:44     ` David Howells
2016-03-08 15:48       ` Petko Manolov
2016-03-08 16:07     ` David Howells
2016-03-08 16:37       ` Petko Manolov
2016-03-08 22:05         ` 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=20160304150120.17121.33822.stgit@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=keyrings@vger.kernel.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
all inboxes | Powered by JetHome®