From: Tadeusz Struk <tstruk@gmail.com>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>,
David Howells <dhowells@redhat.com>
Cc: tadeusz.struk@intel.com, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
linux-crypto@vger.kernel.org, dwmw2@infradead.org
Subject: Re: [RFC PATCH 5/8] KEYS: Provide software public key query function [ver 3]
Date: Wed, 11 May 2016 17:17:10 -0700 [thread overview]
Message-ID: <92771fa9-e5a8-2721-519b-f91da21deb3e@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1605111624090.16566@mjmartin-mac01.local>
On 05/11/2016 04:50 PM, Mat Martineau wrote:
>
>> + len = crypto_akcipher_maxsize(tfm);
>> + info->key_size = len * 8;
>> + info->max_data_size = len;
>> + info->max_sig_size = len;
>> + info->max_enc_size = len;
>> + info->max_dec_size = len;
>
> If len > UINT16_MAX, should UINT16_MAX be reported as the max size? Similar question for len*8 and key_size.
Hi Mat,
Since all the operations performed are mod key->n the output will never be bigger
than size of pkey->n, which is the return value from crypto_akcipher_maxsize(tfm)
for a given key.
Thanks,
--
TS
next prev parent reply other threads:[~2016-05-12 0:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 14:21 [RFC PATCH 0/8] KEYS: keyctl operations for asymmetric keys [ver 3] David Howells
2016-05-11 14:22 ` [RFC PATCH 1/8] KEYS: Provide key type operations for asymmetric key ops " David Howells
2016-05-11 14:22 ` [RFC PATCH 2/8] KEYS: Provide keyctls to drive the new key type ops for asymmetric keys " David Howells
2016-05-11 22:17 ` Mat Martineau
2016-05-12 10:16 ` David Howells
2016-05-12 11:04 ` David Woodhouse
2016-05-11 14:22 ` [RFC PATCH 3/8] KEYS: Provide missing asymmetric key subops for new key type ops " David Howells
2016-05-11 14:22 ` [RFC PATCH 4/8] KEYS: Make the X.509 and PKCS7 parsers supply the sig encoding type " David Howells
2016-05-11 14:22 ` [RFC PATCH 5/8] KEYS: Provide software public key query function " David Howells
2016-05-11 23:50 ` Mat Martineau
2016-05-12 0:17 ` Tadeusz Struk [this message]
2016-05-12 10:19 ` David Howells
2016-05-12 17:01 ` Mat Martineau
2016-05-11 14:22 ` [RFC PATCH 6/8] KEYS: Allow the public_key struct to hold a private key " David Howells
2016-05-11 14:22 ` [RFC PATCH 7/8] KEYS: Implement encrypt, decrypt and sign for software asymmetric " David Howells
2016-05-11 14:22 ` [RFC PATCH 8/8] KEYS: Implement PKCS#8 RSA Private Key parser " David Howells
2016-05-11 19:11 ` David Woodhouse
2016-05-12 0:09 ` Mat Martineau
2016-05-12 10:20 ` 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=92771fa9-e5a8-2721-519b-f91da21deb3e@gmail.com \
--to=tstruk@gmail.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.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 \
/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