linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Kasatkin <d.kasatkin@samsung.com>
To: dhowells@redhat.com, keyrings@linux-nfs.org
Cc: zohar@linux.vnet.ibm.com, linux-ima-devel@lists.sourceforge.net,
	linux-security-module@vger.kernel.org, jmorris@namei.org,
	rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
	dmitry.kasatkin@gmail.com
Subject: Re: [PATCH 0/4] KEYS fixes
Date: Fri, 03 Oct 2014 13:43:00 +0300	[thread overview]
Message-ID: <542E7DB4.2030206@samsung.com> (raw)
In-Reply-To: <cover.1412327306.git.d.kasatkin@samsung.com>

Hi David,

I slightly update what I posted and added one fix and one suggestion on
the top.

Here is those patches on the top of Jame's tree...

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

- Dmitry

On 03/10/14 12:09, Dmitry Kasatkin wrote:
> I reported yesterday problems with new KEYS.
> Module signature verification is broken, integrity subsystem verification is
> broken, kernel oopses.
>
> Here is few fixes.
>
> - Dmitry
>
> Dmitry Kasatkin (4):
>   KEYS: handle error code encoded in pointer
>   KEYS: provide pure subject key identifier (fingerprint) as key id
>   module: search the key only by keyid
>   integrity: do zero padding of the key id
>
>  crypto/asymmetric_keys/asymmetric_type.c  | 27 ++++++++++++++++++++++++---
>  crypto/asymmetric_keys/x509_cert_parser.c |  6 ++++++
>  crypto/asymmetric_keys/x509_parser.h      |  1 +
>  crypto/asymmetric_keys/x509_public_key.c  |  2 ++
>  include/keys/asymmetric-type.h            |  2 +-
>  kernel/module_signing.c                   | 16 +++++-----------
>  security/integrity/digsig_asymmetric.c    |  2 +-
>  7 files changed, 40 insertions(+), 16 deletions(-)
>


  parent reply	other threads:[~2014-10-03 10:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03  9:09 [PATCH 0/4] KEYS fixes Dmitry Kasatkin
2014-10-03  9:09 ` [PATCH 1/4] KEYS: handle error code encoded in pointer Dmitry Kasatkin
2014-10-03  9:09 ` [PATCH 2/4] KEYS: provide pure subject key identifier (fingerprint) as key id Dmitry Kasatkin
2014-10-03  9:09 ` [PATCH 3/4] module: search the key only by keyid Dmitry Kasatkin
2014-10-03  9:09 ` [PATCH 4/4] integrity: do zero padding of the key id Dmitry Kasatkin
2014-10-03 10:43 ` Dmitry Kasatkin [this message]
2014-10-03 12:46 ` [PATCH 3/4] module: search the key only by keyid David Howells
2014-10-03 12:49   ` Dmitry Kasatkin
2014-10-03 12:53     ` Dmitry Kasatkin
2014-10-03 13:08       ` Dmitry Kasatkin
2014-10-03 13:40       ` David Howells
2014-10-03 14:00         ` Dmitry Kasatkin
2014-10-06 12:44         ` James Morris
2014-10-06 17:14           ` Dmitry Kasatkin
2014-10-06 19:39           ` Mimi Zohar
2014-10-03 12:46 ` [PATCH 1/4] KEYS: handle error code encoded in pointer David Howells
2014-10-03 14:19 ` [PATCH 0/4] KEYS fixes Mimi Zohar
2014-10-03 15:54 ` [PATCH] X.509: If available, use the raw subjKeyId to form the key description David Howells
2014-10-06 13:51 ` [PATCH 2/4] KEYS: provide pure subject key identifier (fingerprint) as key id 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=542E7DB4.2030206@samsung.com \
    --to=d.kasatkin@samsung.com \
    --cc=dhowells@redhat.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-ima-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=zohar@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).