[gnutls-devel] GnuTLS | fips: make FIPS140-2 mode enablement logic simpler (!1253)

Development of GNU's TLS library gnutls-devel at lists.gnutls.org
Tue May 19 18:01:30 CEST 2020

Daiki Ueno commented on a discussion on doc/cha-internals.texi: https://gitlab.com/gnutls/gnutls/-/merge_requests/1253#note_345331656

> +configure option.
> +
> +There are two distinct library states with regard to FIPS140-2: the FIPS140-2
> +mode is @emph{installed} if @code{/etc/system-fips} is present, and the
> +FIPS140-2 mode is @emph{enabled} if @code{/proc/sys/crypto/fips_enabled}
> +contains '1', which is typically set with the ``fips=1'' kernel command line
> +option.
> +
> +When the FIPS140-2 mode is installed, the operation of the library is modified
> +as follows.
>  @itemize
> - at item FIPS140-2 mode is enabled when @code{/proc/sys/crypto/fips_enabled} contains '1' and @code{/etc/system-fips} is present.
> - at item Only approved by FIPS140-2 algorithms are enabled
> - at item Only approved by FIPS140-2 key lengths are allowed for key generation
>  @item The random generator used switches to DRBG-AES

I've changed the RNG part to always switch to FIPS RNG if FIPS installed.

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1253#note_345331656
You're receiving this email because of your account on gitlab.com.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20200519/f861c2f8/attachment.html>

More information about the Gnutls-devel mailing list