From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, arnd@arndb.de, jkosina@suse.cz,
keyrings@linux-nfs.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Keyrings, modsigning adjustments
Date: Fri, 23 Jan 2015 13:27:05 +0000 [thread overview]
Message-ID: <27884.1422019625@warthog.procyon.org.uk> (raw)
Hi James,
Could you pull these into security/next? There are the following pieces:
(1) Make /proc/keys unconditional as it's used by libkeyutils now.
(2) Reduce the verbosity of the ASN.1 compiler and the X.509 certificate
collection during building.
Thanks,
David
---
The following changes since commit 961be7ef6963806cb978ccd6acf6bf84b0c63346:
tpm/tpm_tis: Add missing ifdef CONFIG_ACPI for pnp_acpi_device (2015-01-22 13:37:33 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-next-20150123
for you to fetch changes up to e994393acd65e729a574aaca466eab22b5b39cc6:
X.509: silence asn1 compiler debug output (2015-01-23 12:10:39 +0000)
----------------------------------------------------------------
Keyrings changes for next
----------------------------------------------------------------
Arnd Bergmann (2):
X.509: shut up about included cert for silent build
X.509: silence asn1 compiler debug output
David Howells (1):
KEYS: Make /proc/keys unconditional if CONFIG_KEYS=y
Documentation/security/keys.txt | 2 --
kernel/Makefile | 2 +-
scripts/asn1_compiler.c | 30 +++++++++++++++++++-----------
security/keys/Kconfig | 18 ------------------
security/keys/proc.c | 8 --------
5 files changed, 20 insertions(+), 40 deletions(-)
next reply other threads:[~2015-01-23 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 13:27 David Howells [this message]
2015-01-28 23:45 ` 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=27884.1422019625@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=arnd@arndb.de \
--cc=jkosina@suse.cz \
--cc=jmorris@namei.org \
--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
all inboxes | Powered by JetHome®