mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, keyrings@linux-nfs.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] KEYS: Fixes for keyrings
Date: Tue, 16 Sep 2014 17:52:52 +0100	[thread overview]
Message-ID: <32186.1410886372@warthog.procyon.org.uk> (raw)

Hi James,

Can you please pull these fixes and send them on upstream:

 (1) Reinstate the production of EPERM for key types beginning with '.' in
     requests from userspace.

 (2) Tidy up the cleanup of PKCS#7 message signed information blocks and fix a
     bug this made more obvious.

They will also need merging into security/next so that further patches that
depend on them can be applied.

David
---
The following changes since commit 478d085524c57cf4283699f529d5a4c22188ea69:

  Merge tag 'keys-next-20140805' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs into next (2014-08-06 00:52:01 +1000)

are available in the git repository at:


  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-fixes-20140916

for you to fetch changes up to cecf5d2e1208da512a4c951c24acd66c54a4d06c:

  PKCS#7: Fix the parser cleanup to drain parsed out X.509 certs (2014-09-16 17:29:03 +0100)

----------------------------------------------------------------
(from the branch description for keys-fixes local branch)

Keyrings fixes
Keyrings fixes

----------------------------------------------------------------
David Howells (3):
      KEYS: Reinstate EPERM for a key type name beginning with a '.'
      PKCS#7: Provide a single place to do signed info block freeing
      PKCS#7: Fix the parser cleanup to drain parsed out X.509 certs

 crypto/asymmetric_keys/pkcs7_parser.c | 61 +++++++++++++++++++----------------
 security/keys/keyctl.c                |  2 ++
 2 files changed, 35 insertions(+), 28 deletions(-)

             reply	other threads:[~2014-09-16 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 16:52 David Howells [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-16 13:29 David Howells
2014-09-16 14:01 ` David Howells
2014-09-17 23:23   ` James Morris
2014-09-17 23:27   ` David Howells
2014-09-18  7:12     ` James Morris
2014-09-18 13:23     ` David Howells
2014-09-16 16:48 ` 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=32186.1410886372@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 \
    /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®