mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Tadeusz Struk <tadeusz.struk@intel.com>,
	stable@vger.kernel.org,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
	David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 4.3.y] crypto: fix test vector for rsa
Date: Tue, 2 Feb 2016 11:20:53 +0800	[thread overview]
Message-ID: <20160202032053.GC16987@gondor.apana.org.au> (raw)
In-Reply-To: <20160202005253.GA31348@kroah.com>

On Mon, Feb 01, 2016 at 04:52:53PM -0800, Greg KH wrote:
> On Wed, Jan 13, 2016 at 08:57:40PM -0800, Tadeusz Struk wrote:
> > Hi,
> > After the fix to the asn1_decoder in commit: 0d62e9dd
> > "ASN.1: Fix non-match detection failure on data overrun"
> > the rsa algorithm is failing to register in 4.3 stable kernels with
> > error: "alg: rsa: test failed on vector 4, err=-74"
> > 
> > This happens because the asn1 definition for the rsa key that has been
> > added in 4.2 defined all 3 components of the key as non-optional, as
> > the asn1_decoder before the fix was working fine for both the private
> > and public keys.
> > 
> > This patch adds the missing (fake) component to one key vector to allow
> > the algorithm to successfully register and be used with a valid private
> > keys later. This is only to make the asn1_decoder successfully parse the
> > key and the fake component is never used in the test as the vector is
> > marked as public key.
> > 
> > This patch applies only to 4.3 kernels as the 4.2 version of asn1_decoder
> > works fine with the asn1 definition.
> > 4.4 is also ok because the akcipher interface has been changed, and
> > the set_key function has been split into set_public_key and set_priv_key
> > and there are two separate asn1 definitions for the two key formats
> > with all the required components correctly defined (commit 22287b0).
> > 
> > Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
> > ---
> > diff --git a/crypto/testmgr.h b/crypto/testmgr.h
> > index 64b8a80..450f30e 100644
> > --- a/crypto/testmgr.h
> > +++ b/crypto/testmgr.h
> > @@ -270,7 +270,7 @@ static struct akcipher_testvec rsa_tv_template[] = {
> >  	.c_size = 256,
> >  	}, {
> >  	.key =
> > -	"\x30\x82\x01\x09" /* sequence of 265 bytes */
> > +	"\x30\x82\x01\x0C" /* sequence of 268 bytes */
> >  	"\x02\x82\x01\x00" /* modulus - integer of 256 bytes */
> >  	"\xDB\x10\x1A\xC2\xA3\xF1\xDC\xFF\x13\x6B\xED\x44\xDF\xF0\x02\x6D"
> >  	"\x13\xC7\x88\xDA\x70\x6B\x54\xF1\xE8\x27\xDC\xC3\x0F\x99\x6A\xFA"
> > @@ -288,8 +288,9 @@ static struct akcipher_testvec rsa_tv_template[] = {
> >  	"\x55\xE6\x29\x69\xD1\xC2\xE8\xB9\x78\x59\xF6\x79\x10\xC6\x4E\xEB"
> >  	"\x6A\x5E\xB9\x9A\xC7\xC4\x5B\x63\xDA\xA3\x3F\x5E\x92\x7A\x81\x5E"
> >  	"\xD6\xB0\xE2\x62\x8F\x74\x26\xC2\x0C\xD3\x9A\x17\x47\xE6\x8E\xAB"
> > -	"\x02\x03\x01\x00\x01", /* public key - integer of 3 bytes */
> > -	.key_len = 269,
> > +	"\x02\x03\x01\x00\x01" /* public key - integer of 3 bytes */
> > +	"\x02\x01\x00", /* private key - integer of 1 byte */
> > +	.key_len = 272,
> >  	.m = "\x54\x85\x9b\x34\x2c\x49\xea\x2a",
> >  	.c =
> >  	"\xb2\x97\x76\xb4\xae\x3e\x38\x3c\x7e\x64\x1f\xcc\xa2\x7f\xf6\xbe"
> > 
> 
> I need an ack from the maintainer of this subsystem before I can take a
> patch that is not already upstream in Linus's tree...

Acked-by: Herbert Xu <herbert@gondor.apana.org.au>

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2016-02-02  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  4:57 Tadeusz Struk
2016-02-02  0:52 ` Greg KH
2016-02-02  3:20   ` Herbert Xu [this message]
2016-02-14 21:04 ` Patch "crypto: fix test vector for rsa" has been added to the 4.3-stable tree gregkh

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=20160202032053.GC16987@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®