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, keyrings@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: [GIT PULL] KEYS: Miscellany
Date: Fri, 08 Jul 2016 19:15:15 +0100	[thread overview]
Message-ID: <19217.1468001715@warthog.procyon.org.uk> (raw)

Hi James,

Could you pull these patches into security/next please?  They've been in
linux-next for 3 weeks or so.

One patch just strips a bunch of spaces and the other patch changes sign-file
to attempt to acertain as to whether an X.509 cert is in DER or PEM format
before trying to read it and then parsing it using the appropriate openssl
call.

Thanks,
David
---
The following changes since commit 40d273782ff16fe1a7445cc05c66a447dfea3433:

  security: tomoyo: simplify the gc kthread creation (2016-06-06 20:23:55 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-misc-20160708

for you to fetch changes up to 9552c7aebb8c36912612fddad5b55267c671a303:

  modsign: Make sign-file determine the format of the X.509 cert (2016-06-14 13:18:33 +0100)

----------------------------------------------------------------
Keyrings miscellany

----------------------------------------------------------------
David Howells (2):
      KEYS: Strip trailing spaces
      modsign: Make sign-file determine the format of the X.509 cert

 include/keys/rxrpc-type.h   |  2 +-
 scripts/sign-file.c         | 34 ++++++++++++++++++++++++++--------
 security/keys/persistent.c  |  2 +-
 security/keys/request_key.c |  2 +-
 4 files changed, 29 insertions(+), 11 deletions(-)

             reply	other threads:[~2016-07-08 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 18:15 David Howells [this message]
2019-05-29 22:01 [GIT PULL] keys: Miscellany David Howells
2019-05-29 22:11 ` Eric Biggers
2019-05-30  6:53 ` 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=19217.1468001715@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@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

Powered by JetHome