mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org, jmorris@namei.org
Cc: dhowells@redhat.com, keyrings@linux-nfs.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] Keys patches
Date: Fri, 13 Dec 2013 15:45:08 +0000	[thread overview]
Message-ID: <20131213154508.3155.20275.stgit@warthog.procyon.org.uk> (raw)


Hi Linus, James,

Here are some more keyrings fixes plus some module signing documentation (if
you want it).  They can be found here also:

	http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-devel

There are four items:

 (1) A patch to fix X.509 certificate gathering.  The problem was that I was
     coming up with a different path for signing_key.x509 in the build
     directory if it didn't exist to if it did exist.  This meant that the
     X.509 cert container object file would be rebuilt on the second rebuild in
     a build directory and the kernel would get relinked.

 (2) Unconditionally remove files generated by SYSTEM_TRUSTED_KEYRING=y when
     doing make mrproper.

 (3) Actually initialise the persistent-keyring semaphore for init_user_ns.  I
     have no idea why this works at all for users in the base user namespace
     unless it's something to do with systemd containerising the system.

 (4) Documentation for module signing.  Do you want this now or the next merge
     window?

David
---
David Howells (1):
      X.509: Fix certificate gathering

James Solner (1):
      Add Documentation/module-signing.txt file

Kirill Tkhai (1):
      KEYS: Remove files generated when SYSTEM_TRUSTED_KEYRING=y

Xiao Guangrong (1):
      KEYS: fix uninitialized persistent_keyring_register_sem


 Documentation/module-signing.txt |  240 ++++++++++++++++++++++++++++++++++++++
 kernel/Makefile                  |    7 +
 kernel/user.c                    |    6 -
 3 files changed, 247 insertions(+), 6 deletions(-)
 create mode 100644 Documentation/module-signing.txt


             reply	other threads:[~2013-12-13 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 15:45 David Howells [this message]
2013-12-13 15:45 ` [PATCH 1/4] X.509: Fix certificate gathering David Howells
2013-12-13 15:45 ` [PATCH 2/4] KEYS: Remove files generated when SYSTEM_TRUSTED_KEYRING=y David Howells
2013-12-13 15:45 ` [PATCH 3/4] KEYS: fix uninitialized persistent_keyring_register_sem David Howells
2013-12-13 15:45 ` [PATCH 4/4] Add Documentation/module-signing.txt file David Howells
2013-12-13 16:00 ` [PATCH 1/4] X.509: Fix certificate gathering 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=20131213154508.3155.20275.stgit@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®