mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: [GIT PULL] security: keyrings and modsign fixes
Date: Tue, 29 Sep 2015 19:30:52 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.20.1509291928530.25162@namei.org> (raw)

Please pull these keyrings and modsign fixes from David Howells.

The following changes since commit 3225031fbeb1e32b269a82eccd815128267a4bfe:

  Merge branch 'stable' of git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile (2015-09-28 12:27:18 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git for-linus

for you to fetch changes up to 0266715155379820c5c626e2cd4b8c91751036bc:

  Merge tag 'keys-fixes-20150925' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs into for-linus (2015-09-29 19:19:09 +1000)

----------------------------------------------------------------

David Howells (4):
      KEYS: Fix race between key destruction and finding a keyring by name
      KEYS: Remove unnecessary header #inclusions from extract-cert.c
      X.509: Don't strip leading 00's from key ID when constructing key description
      MODSIGN: Change from CMS to PKCS#7 signing if the openssl is too old

James Morris (1):
      Merge tag 'keys-fixes-20150925' of git://git.kernel.org/.../dhowells/linux-fs into for-linus

 Documentation/Changes                    |  2 +-
 crypto/asymmetric_keys/x509_public_key.c |  4 --
 scripts/extract-cert.c                   |  4 --
 scripts/sign-file.c                      | 94 ++++++++++++++++++++++++++------
 security/keys/gc.c                       |  8 +--
 5 files changed, 82 insertions(+), 30 deletions(-)

                 reply	other threads:[~2015-09-29  9:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LRH.2.20.1509291928530.25162@namei.org \
    --to=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®