On Wed, Jul 03, 2024 at 11:51:21PM +0200, William Lallemand wrote: > > aws-lc implements chacha20_poly1305 in a different way than QuicTLS. > > and if that gap is eliminated, it will be a good point to declare aws-lc as > > a recommended QUIC lib. > > > > if we compare aws-lc against openssl-1.1 (not quictls), it is indeed > > matches (maybe except some niche features like async) > > > > BoringSSL, LibreSSL, and AWS-LC uses the EVP_AEAD API, basically we would need > to use EVP_aead_chacha20_poly1305() instead of EVP_chacha20_poly1305(), and > EVP_aead_chacha20_poly1305() instead of EVP_chacha20() and uses the EVP_AEAD > functions. IMHO this is not a huge change and this is doable, we just need to > invest some time on it. > > Regards,
FYI I just push some patches that implements the CHACHA20_POLY1305 for QUIC with AWS-LC. We now handle with AWS-LC for QUIC: - TLS_AES_128_GCM_SHA256 - TLS_AES_256_GCM_SHA384 - TLS_CHACHA20_POLY1305_SHA256 The TLS_AES_128_CCM_SHA256 cipher is not implemented by AWS-LC, and is disabled by default in a lot of stack anyway. Regards, -- William Lallemand
