From: David Howells <dhowells@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dhowells@redhat.com,
Mat Martineau <mathew.j.martineau@linux.intel.com>,
dwmw2@infradead.org, tadeusz.struk@intel.com,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, "Theodore Ts'o" <tytso@mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH 5/8] KEYS: Provide software public key query function [ver #2]
Date: Fri, 24 Jun 2016 13:06:02 +0100 [thread overview]
Message-ID: <7446.1466769962@warthog.procyon.org.uk> (raw)
In-Reply-To: <20160624100215.GA19150@gondor.apana.org.au>
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> IOW exporting the raw RSA might make sense because the key may
> not be visible to user-space, or that the RSA might be implemented
> in hardware offload, but there is no sane reason to export pkcs1pad.
The problem is that if I'm to produce consistency with, say, the TPM
interface, then I have to deal in wrapped/padded data - leastways as far as I
can tell from reading the docs.
David
next prev parent reply other threads:[~2016-06-24 12:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 13:47 [PATCH 0/8] KEYS: keyctl operations for asymmetric keys [ver #2] David Howells
2016-06-23 13:47 ` [PATCH 1/8] KEYS: Provide key type operations for asymmetric key ops " David Howells
2016-06-23 13:47 ` [PATCH 2/8] KEYS: Provide keyctls to drive the new key type ops for asymmetric keys " David Howells
2016-07-28 23:21 ` Mat Martineau
2016-06-23 13:47 ` [PATCH 3/8] KEYS: Provide missing asymmetric key subops for new key type ops " David Howells
2016-06-23 13:48 ` [PATCH 4/8] KEYS: Make the X.509 and PKCS7 parsers supply the sig encoding type " David Howells
2016-06-23 13:48 ` [PATCH 5/8] KEYS: Provide software public key query function " David Howells
2016-06-23 15:46 ` Mat Martineau
2016-06-24 10:02 ` Herbert Xu
2016-06-24 12:06 ` David Howells [this message]
2016-06-25 1:37 ` Herbert Xu
2016-06-27 14:27 ` David Howells
2016-06-28 4:54 ` Herbert Xu
2016-06-23 13:48 ` [PATCH 6/8] KEYS: Allow the public_key struct to hold a private key " David Howells
2016-06-23 13:48 ` [PATCH 7/8] KEYS: Implement encrypt, decrypt and sign for software asymmetric " David Howells
2016-06-23 13:48 ` [PATCH 8/8] KEYS: Implement PKCS#8 RSA Private Key parser " David Howells
2017-10-05 22:59 ` [PATCH 0/8] KEYS: keyctl operations for asymmetric keys " George Wilson
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=7446.1466769962@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=tadeusz.struk@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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