Re: [PATCH 1/4] crypto: implement workaround for GNUTLS thread safety problems

2025-07-21 Thread Fabiano Rosas
Daniel P. Berrangé writes: > When TLS 1.3 is negotiated on a TLS session, GNUTLS will perform > automatic rekeying of the session after 16 million records. This > is done for all algorithms except CHACHA20_POLY1305 which does > not require rekeying. > > Unfortunately the rekeying breaks GNUTLS' p

Re: [PATCH 1/4] crypto: implement workaround for GNUTLS thread safety problems

2025-07-21 Thread Fabiano Rosas
Daniel P. Berrangé writes: > When TLS 1.3 is negotiated on a TLS session, GNUTLS will perform > automatic rekeying of the session after 16 million records. This > is done for all algorithms except CHACHA20_POLY1305 which does > not require rekeying. > > Unfortunately the rekeying breaks GNUTLS' p

[PATCH 1/4] crypto: implement workaround for GNUTLS thread safety problems

2025-07-18 Thread Daniel P . Berrangé
When TLS 1.3 is negotiated on a TLS session, GNUTLS will perform automatic rekeying of the session after 16 million records. This is done for all algorithms except CHACHA20_POLY1305 which does not require rekeying. Unfortunately the rekeying breaks GNUTLS' promise that it is safe to use a gnutls_s