From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: "Stephan Müller" <smueller@chronox.de>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Problem with RSA test from testmgr
Date: Thu, 2 Mar 2017 07:21:58 +0100 [thread overview]
Message-ID: <20170302062158.GA9242@Red> (raw)
In-Reply-To: <45107561.YcGaMWr4ZQ@tauon.atsec.com>
On Wed, Mar 01, 2017 at 04:07:17PM +0100, Stephan Müller wrote:
> Am Mittwoch, 1. März 2017, 13:04:14 CET schrieb Corentin Labbe:
>
> Hi Corentin,
>
> >
> > I got the following:
> >
> > [ 1.086228] alg: akcipher: encrypt test failed. Invalid output
> > [ 1.092196] 00000000: 6e 7c 8a 75 e7 30 80 d1 5e ab 9b db a2 cf ed db
> > [ 1.098882] 00000010: c9 b2 db 43 bd 9a b9 75 27 f3 73 d9 73 b7 81 8c
> > [ 1.105524] 00000020: 49 e8 45 fc 43 44 f5 6d f0 f7 b8 f2 ae 6b ae 49
> > [ 1.112090] 00000030: 1b 8e 50 c6 88 4e 99 09 78 14 f2 5d 99 c3 7f f9
> > [ 1.118747] alg: akcipher: test 1 failed for rsa-generic, err=-22
> > (Exactly the output of my hardare and openssl test)
> >
> > So the problem is just that my hardware does not handle non-padded data.
>
> I guess the best course of action would be to patch the test vector to use the
> padded data.
>
> Ciao
> Stephan
I am finishing a patch that made testmgr test both (padded and unpadded).
Regards
Corentin Labbe
next prev parent reply other threads:[~2017-03-02 6:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 15:59 Problem with RSA test from testmgr Corentin Labbe
2017-02-28 16:08 ` Stephan Müller
2017-02-28 16:45 ` Corentin Labbe
2017-02-28 22:35 ` Stephan Müller
2017-03-01 12:04 ` Corentin Labbe
2017-03-01 15:07 ` Stephan Müller
2017-03-02 6:21 ` Corentin Labbe [this message]
2017-03-02 16:30 ` Tadeusz Struk
2017-03-02 2:15 ` Tadeusz Struk
2017-03-02 6:08 ` Stephan Müller
2017-03-02 16:26 ` Tadeusz Struk
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=20170302062158.GA9242@Red \
--to=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
/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.