mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
	dwmw2@infradead.org, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, keyrings@vger.kernel.org
Subject: [GIT PULL] Move cert handling to certs/ directory
Date: Mon, 24 Aug 2015 13:51:52 +0100	[thread overview]
Message-ID: <29947.1440420712@warthog.procyon.org.uk> (raw)

Hi James,

Sorry for the late request, but can you pull this please?  It's a set of
commits that puts a bit of polish on the previous module signing patches.
It moves the certificate handling to its own directory rather than sharing
in the kernel/ directory.  It then moves 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.

David
---
The following changes since commit 0e38c35815f50e5a347977d76fb5eb4c3bf020b5:

  Merge branch 'smack-for-4.3' of https://github.com/cschaufler/smack-next into next (2015-08-14 17:35:10 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/modsign-pkcs7-20150814

for you to fetch changes up to 3ee550f12c1529a023f71c9b5becb3351911047b:

  modsign: Handle signing key in source tree (2015-08-14 16:32:52 +0100)

----------------------------------------------------------------
Module signing with PKCS#7

----------------------------------------------------------------
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 +++++++++++++++++++++
 {kernel => certs}/system_certificates.S |   4 +-
 {kernel => certs}/system_keyring.c      |   0
 crypto/Kconfig                          |   1 +
 init/Kconfig                            |  39 ---------
 kernel/Makefile                         | 143 --------------------------------
 scripts/Kbuild.include                  |  51 ++++++++++++
 11 files changed, 212 insertions(+), 198 deletions(-)
 create mode 100644 certs/Kconfig
 create mode 100644 certs/Makefile
 rename {kernel => certs}/system_certificates.S (86%)
 rename {kernel => certs}/system_keyring.c (100%)

             reply	other threads:[~2015-08-24 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 12:51 David Howells [this message]
2015-08-25 22:26 ` James Morris

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=29947.1440420712@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jmorris@namei.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®