From: Denis Kenzior <denkenz@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
James Prestwood <prestwoj@gmail.com>
Subject: Re: Linux 6.5 broke iwd
Date: Thu, 12 Oct 2023 10:08:46 -0500 [thread overview]
Message-ID: <c917020d-0cb0-4289-a2e3-d9a0fa28151a@gmail.com> (raw)
In-Reply-To: <ZSgChGwi1r9CILPI@gondor.apana.org.au>
Hi Herbert,
> OK, we need to take a step back. The commits that you're testing
> are all known to be buggy.
>
> So please tell me what exactly is the problem with the latest kernel
> and then we can work it back from there.
Looks like something took out the ability to run sign/verify without a hash on
asymmetric keys.
>
> If you have a reproducer that works on the latest kernel that would
> be great.
>
Easiest is to run the ell unit test:
[denkenz@archdev tmp]$ git clone git://git.kernel.org/pub/scm/libs/ell/ell.git
[denkenz@archdev tmp]$ cd ell
[denkenz@archdev ell]$ ./bootstrap-configure
[denkenz@archdev ell]$ make -j16
[denkenz@archdev ell]$ unit/test-key
TEST: unsupported
TEST: user key
TEST: Diffie-Hellman 1
TEST: Diffie-Hellman 2
TEST: Diffie-Hellman 3
TEST: simple keyring
TEST: trusted keyring
TEST: trust chain
TEST: key crypto
test-key: unit/test-key.c:624: test_key_crypto: Assertion `len ==
sizeof(ciphertext)' failed.
Regards,
-Denis
next prev parent reply other threads:[~2023-10-12 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 17:11 Linux 6.5 broke iwd Denis Kenzior
2023-10-12 0:38 ` Herbert Xu
2023-10-12 2:18 ` Denis Kenzior
2023-10-12 2:26 ` Herbert Xu
2023-10-12 2:33 ` Herbert Xu
2023-10-12 3:09 ` Denis Kenzior
2023-10-12 3:28 ` Herbert Xu
2023-10-12 14:19 ` Denis Kenzior
2023-10-12 14:28 ` Herbert Xu
2023-10-12 15:08 ` Denis Kenzior [this message]
2023-10-16 8:35 ` [PATCH] KEYS: asymmetric: Fix sign/verify on pkcs1pad without a hash Herbert Xu
2023-10-16 19:37 ` Denis Kenzior
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=c917020d-0cb0-4289-a2e3-d9a0fa28151a@gmail.com \
--to=denkenz@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=prestwoj@gmail.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