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@linux-nfs.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] KEYS: Miscellaneous fixes
Date: Wed, 10 Sep 2014 22:21:54 +0100	[thread overview]
Message-ID: <20140910212154.10752.23343.stgit@warthog.procyon.org.uk> (raw)


Hi James,

Here are some fixes to go upstream:

 (1) Fix a bug in the assoc_array garbage collector [CVE-2014-3631].

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

 (3) Fix some missing 'static' annotations.

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

They can be found here also:

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

Tagged with:

	keys-fixes-20140910

David
---
David Howells (6):
      KEYS: Fix termination condition in assoc array garbage collection
      KEYS: Reinstate EPERM for a key type name beginning with a '.'
      KEYS: Fix missing statics
      PKCS#7: Add a missing static
      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 ++++++++++++++++++---------------
 crypto/asymmetric_keys/pkcs7_trust.c  |    6 ++-
 lib/assoc_array.c                     |    4 ++
 security/keys/keyctl.c                |    2 +
 security/keys/request_key_auth.c      |    4 +-
 5 files changed, 43 insertions(+), 34 deletions(-)


             reply	other threads:[~2014-09-10 21:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 21:21 David Howells [this message]
2014-09-10 21:22 ` [PATCH 1/6] KEYS: Fix termination condition in assoc array garbage collection David Howells
2014-09-10 21:22 ` [PATCH 2/6] KEYS: Reinstate EPERM for a key type name beginning with a '.' David Howells
2014-09-10 23:36   ` Mimi Zohar
2014-09-11 11:43     ` Mimi Zohar
2014-09-11 12:09     ` David Howells
2014-09-11 12:27       ` Dmitry Kasatkin
2014-09-11 12:28         ` Dmitry Kasatkin
2014-09-11 13:46         ` Mimi Zohar
2014-09-11 21:26         ` David Howells
2014-09-10 21:22 ` [PATCH 3/6] KEYS: Fix missing statics David Howells
2014-09-10 21:22 ` [PATCH 4/6] PKCS#7: Add a missing static David Howells
2014-09-10 21:22 ` [PATCH 5/6] PKCS#7: Provide a single place to do signed info block freeing David Howells
2014-09-10 21:22 ` [PATCH 6/6] PKCS#7: Fix the parser cleanup to drain parsed out X.509 certs David Howells
2014-09-15 13:04 ` [PATCH 0/6] KEYS: Miscellaneous fixes David Howells
2014-09-16  2:15   ` James Morris
2014-09-16  9:07   ` 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=20140910212154.10752.23343.stgit@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®