[gnutls-devel] GnuTLS | Mark HKDF and AES-GCM as approved when used in TLS (!1568)

[Read-only notification of GnuTLS library development activities]

Merge request https://gitlab.com/gnutls/gnutls/-/merge_requests/1568 was reviewed by Daiki Ueno

--
  
Daiki Ueno started a new discussion on lib/crypto-api.h: https://gitlab.com/gnutls/gnutls/-/merge_requests/1568#note_899906008

>  
> +int
> +_gnutls_cipher_init_handle(gnutls_cipher_hd_t * handle,

I don't think we need to introduce a new internal function for AES-GCM. TLS code already uses `_gnutls_aead_cipher_init` (for [TLS 1.3](https://gitlab.com/gnutls/gnutls/-/blob/fe72ba937cdfe747ed9dfd549c97ce01c2a234d0/lib/constate.c#L1293)) or `_gnutls_auth_cipher_init` (for [TLS 1.2](https://gitlab.com/gnutls/gnutls/-/blob/fe72ba937cdfe747ed9dfd549c97ce01c2a234d0/lib/constate.c#L571)), neither of which changes FIPS context.


-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1568
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/20220404/946f8894/attachment.html>