From: joeyli <jlee@suse.com>
To: rusty@rustcorp.com.au, dhowells@redhat.com,
herbert@gondor.hengli.com.au, linux-kernel@vger.kernel.org,
davem@davemloft.net, Randy Dunlap <rdunlap@xenotime.net>,
Josh Boyer <jwboyer@redhat.com>
Subject: Re: [PATCH] asymmetric keys: explicitly add the leading zero byte to encoded message
Date: Tue, 16 Jul 2013 10:36:18 +0800 [thread overview]
Message-ID: <1373942178.6260.36.camel@linux-s257.site> (raw)
In-Reply-To: <1373598691-1504-1-git-send-email-jlee@suse.com>
Hi all experts,
Does there have any suggestions or comments for this patch to asymmetric
keys?
Thanks a lot!
Joey Lee
於 五,2013-07-12 於 11:11 +0800,Lee, Chun-Yi 提到:
> From: Chun-Yi Lee <jlee@suse.com>
>
> Per PKCS1 spec, the EMSA-PKCS1-v1_5 encoded message is leading by 0x00 0x01 in
> its first 2 bytes. The leading zero byte is suppressed by MPI so we pass a
> pointer to the _preceding_ byte to RSA_verify() in original code, but it has
> risk for the byte is not zero because it's not in EM buffer's scope, neither
> RSA_verify() nor mpi_get_buffer() didn't take care the leading byte.
>
> To avoid the risk, that's better we explicitly add the leading zero byte to EM
> for pass to RSA_verify(). This patch allocate a _EM buffer to capture the
> result from RSA_I2OSP(), then set the first byte to zero in EM and copy the
> remaining bytes from _EM.
>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Josh Boyer <jwboyer@redhat.com>
> Cc: Randy Dunlap <rdunlap@xenotime.net>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: David Howells <dhowells@redhat.com>
> Signed-off-by: Chun-Yi Lee <jlee@suse.com>
> ---
> crypto/asymmetric_keys/rsa.c | 14 ++++++++++----
> 1 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/crypto/asymmetric_keys/rsa.c b/crypto/asymmetric_keys/rsa.c
> index ca1a4f3..7bc99d2 100644
> --- a/crypto/asymmetric_keys/rsa.c
> +++ b/crypto/asymmetric_keys/rsa.c
> @@ -303,6 +303,7 @@ static int RSA_verify_signature(const struct public_key *key,
> /* Variables as per RFC3447 sec 8.2.2 */
> const u8 *H = sig->digest;
> u8 *EM = NULL;
> + u8 *_EM = NULL;
> MPI m = NULL;
> size_t k;
>
> @@ -337,14 +338,19 @@ static int RSA_verify_signature(const struct public_key *key,
> /* (2c) Convert the message representative (m) to an encoded message
> * (EM) of length k octets.
> *
> - * NOTE! The leading zero byte is suppressed by MPI, so we pass a
> - * pointer to the _preceding_ byte to RSA_verify()!
> + * NOTE! The leading zero byte is suppressed by MPI, so we add it
> + * back to EM before input to RSA_verify()!
> */
> - ret = RSA_I2OSP(m, k, &EM);
> + ret = RSA_I2OSP(m, k, &_EM);
> if (ret < 0)
> goto error;
>
> - ret = RSA_verify(H, EM - 1, k, sig->digest_size,
> + EM = kmalloc(k, GFP_KERNEL);
> + memset(EM, 0, 1);
> + memcpy(EM + 1, _EM, k-1);
> + kfree(_EM);
> +
> + ret = RSA_verify(H, EM, k, sig->digest_size,
> RSA_ASN1_templates[sig->pkey_hash_algo].data,
> RSA_ASN1_templates[sig->pkey_hash_algo].size);
>
next prev parent reply other threads:[~2013-07-16 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 3:11 [PATCH] asymmetric keys: explicitly add the leading zero byte to encoded message Lee, Chun-Yi
2013-07-16 2:36 ` joeyli [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-01 3:05 Lee, Chun-Yi
2013-07-02 8:53 joeyli.kernel
2013-06-27 13:32 Lee, Chun-Yi
2013-06-16 4:52 Lee, Chun-Yi
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=1373942178.6260.36.camel@linux-s257.site \
--to=jlee@suse.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.