From: Petr Vorel <pvorel@suse.cz>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>
Subject: ELIBBAD vs. ENOENT for ciphers not allowed by FIPS
Date: Wed, 22 Dec 2021 20:11:07 +0100 [thread overview]
Message-ID: <YcN4S7NIV9F0XXPP@pevik> (raw)
Hi Herbert,
do I understand the crypto code correctly, that although crypto/testmgr.c in
alg_test() returns -EINVAL for non-fips allowed algorithms (that means
failing crypto API test) the API in crypto_alg_lookup() returns -ELIBBAD for
failed test?
Why ELIBBAD and not ENOENT like for missing ciphers? To distinguish between
missing cipher and disabled one due fips?
Kind regards,
Petr
next reply other threads:[~2021-12-22 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 19:11 Petr Vorel [this message]
2021-12-22 22:08 ` ELIBBAD vs. ENOENT for ciphers not allowed by FIPS Herbert Xu
2021-12-22 22:25 ` Eric Biggers
2021-12-22 22:31 ` Herbert Xu
2021-12-22 22:45 ` Eric Biggers
2021-12-23 8:21 ` Petr Vorel
2021-12-23 15:08 ` Eric Biggers
2021-12-27 5:52 ` Herbert Xu
2021-12-27 5:51 ` Herbert Xu
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=YcN4S7NIV9F0XXPP@pevik \
--to=pvorel@suse.cz \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/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