mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: linux-security-module <linux-security-module@vger.kernel.org>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Dmitry Kasatkin <d.kasatkin@samsung.com>,
	David Howells <dhowells@redhat.com>,
	Josh Boyer <jwboyer@redhat.com>,
	keyrings <keyrings@linux-nfs.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH v4 0/4] ima: extending secure boot certificate chain
Date: Wed, 28 May 2014 11:09:40 -0400	[thread overview]
Message-ID: <1401289784-31340-1-git-send-email-zohar@linux.vnet.ibm.com> (raw)

The original patches extended the secure boot signature chain of trust
to IMA-appraisal, by allowing only certificates signed by a 'trusted'
key on the system_trusted_keyring to be added to the IMA keyring.

There were a number of issues with the original patch set, including
kbuild issues, which have been resolved, and with the special dot
prefixed keyrings.  The function key_get_type_from_user(), verfies
the '_type', not the '_description', is dot prefixed.  The previous
version added an additional test, but left the existing check in
key_get_type_from_user().  This patch set removes the unnecessary
dot check.

Previous versions attempted to verify a certificate is signed by a
trusted key, but not necessarily by any key on the system_trusted_keyring.
The first attempt, permitted any key on the targeted trusted keyring
to verify a certificate. This introduced concerns of transitive trust.
The subsequent attempt defined a separate keyring, associated with
each targeted trusted keyring.  This patch set defines a single new
owner_trusted_keyring.

thanks,

Mimi

Mimi Zohar (4):
  KEYS: special dot prefixed keyring name bug fix
  KEYS: verify a certificate is signed by a 'trusted' key
  ima: define '.ima' as a builtin 'trusted' keyring
  KEYS: define an owner trusted keyring

 crypto/asymmetric_keys/x509_public_key.c | 85 +++++++++++++++++++++++++++++++-
 include/keys/system_keyring.h            | 13 +++++
 include/linux/key.h                      |  4 ++
 kernel/system_keyring.c                  | 85 ++++++++++++++++++++++++++++++++
 security/integrity/digsig.c              | 26 +++++++++-
 security/integrity/ima/Kconfig           |  8 +++
 security/integrity/ima/ima_appraise.c    | 11 +++++
 security/integrity/integrity.h           |  5 ++
 security/keys/key.c                      | 20 ++++++++
 security/keys/keyctl.c                   |  6 ++-
 10 files changed, 259 insertions(+), 4 deletions(-)

-- 
1.8.1.4


             reply	other threads:[~2014-05-28 15:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 15:09 Mimi Zohar [this message]
2014-05-28 15:09 ` [RFC PATCH v4 1/4] KEYS: special dot prefixed keyring name bug fix Mimi Zohar
2014-05-30 15:58   ` Dmitry Kasatkin
2014-05-30 17:58     ` Mimi Zohar
     [not found]       ` <CACE9dm-n4R9CSjfzpzCaYrSWDxCOsgX7w2Cvn4gkR6-Z82Qypg@mail.gmail.com>
2014-05-30 19:12         ` Mimi Zohar
2014-05-30 20:45           ` Dmitry Kasatkin
2014-05-28 15:09 ` [RFC PATCH v4 2/4] KEYS: verify a certificate is signed by a 'trusted' key Mimi Zohar
2014-05-28 15:09 ` [RFC PATCH v4 3/4] ima: define '.ima' as a builtin 'trusted' keyring Mimi Zohar
2014-05-28 18:55   ` Dmitry Kasatkin
2014-05-28 19:26     ` Mimi Zohar
2014-05-30 16:05       ` Dmitry Kasatkin
2014-06-09 11:06         ` Mimi Zohar
2014-06-09 11:43           ` Dmitry Kasatkin
2014-05-28 15:09 ` [RFC PATCH v4 4/4] KEYS: define an owner trusted keyring Mimi Zohar
2014-05-30 22:37   ` Dmitry Kasatkin
2014-06-01  2:14     ` Mimi Zohar
2014-06-02 10:48       ` Dmitry Kasatkin
2014-06-02 11:33         ` Mimi Zohar
2014-06-02 11:40           ` Dmitry Kasatkin
2014-06-02 11:54             ` Mimi Zohar
2014-06-02 11:55             ` Josh Boyer
2014-06-03 15:02               ` 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=1401289784-31340-1-git-send-email-zohar@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=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 \
    /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

Powered by JetHome