mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: keyrings@vger.kernel.org
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
	dwmw2@infradead.org, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: [PATCH 0/3] Move cert handling to certs/ directory
Date: Fri, 14 Aug 2015 16:56:50 +0100	[thread overview]
Message-ID: <20150814155650.23941.76513.stgit@warthog.procyon.org.uk> (raw)


Here's a set of patches that moves the certificate handling to its own
directory rather than sharing in the kernel/ directory.  We then move key
generation into the certs/ directory rather than doing it in the root.

This allows us to simplify the kernel/Makefile and slightly simplify the
new certs/Makefile.  It also keeps the various generated files in the same
place to make them easier to find and clean up.

The patches can be found here also:

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

and are tagged with:

	modsign-pkcs7-20150814

David
---
David Howells (1):
      Move certificate handling to its own directory

David Woodhouse (2):
      modsign: Use if_changed rule for extracting cert from module signing key
      modsign: Handle signing key in source tree


 Documentation/module-signing.txt |   18 ++--
 MAINTAINERS                      |    9 ++
 Makefile                         |    9 +-
 certs/Kconfig                    |   42 ++++++++++
 certs/Makefile                   |   94 +++++++++++++++++++++++
 certs/system_certificates.S      |   23 ++++++
 certs/system_keyring.c           |  157 ++++++++++++++++++++++++++++++++++++++
 crypto/Kconfig                   |    1 
 init/Kconfig                     |   39 ---------
 kernel/Makefile                  |  143 -----------------------------------
 kernel/system_certificates.S     |   23 ------
 kernel/system_keyring.c          |  157 --------------------------------------
 scripts/Kbuild.include           |   51 ++++++++++++
 13 files changed, 390 insertions(+), 376 deletions(-)
 create mode 100644 certs/Kconfig
 create mode 100644 certs/Makefile
 create mode 100644 certs/system_certificates.S
 create mode 100644 certs/system_keyring.c
 delete mode 100644 kernel/system_certificates.S
 delete mode 100644 kernel/system_keyring.c


             reply	other threads:[~2015-08-14 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 15:56 David Howells [this message]
2015-08-14 15:57 ` [PATCH 1/3] Move certificate handling to its own directory David Howells
2015-08-14 15:57 ` [PATCH 2/3] modsign: Use if_changed rule for extracting cert from module signing key David Howells
2015-08-14 15:57 ` [PATCH 3/3] modsign: Handle signing key in source tree 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=20150814155650.23941.76513.stgit@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.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

all inboxes | Powered by JetHome®