Re: ELIBBAD vs. ENOENT for ciphers not allowed by FIPS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 22, 2021 at 04:25:07PM -0600, Eric Biggers wrote:
>
> Isn't it just an implementation detail that !fips_allowed is handled by the
> self-test?  Wouldn't it make more sense to report ENOENT for such algorithms?

ELIBBAD does not necessarily mean !fips_allowed, it could also
mean a specific implementation (or hardware) failed the self-test.

Yes, we could change ELIBBAD to something else in the case of
!fips_allowed, but it's certainly not a trivial change.

Please give a motivation for this.

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



[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux