X25519 can be disabled via the API, but upstream BoringSSL doesn't have a good way to disable ChaCha20Poly1305, which we want to do in some contexts. (This is currently implemented with setting an obsolete compliance policy via set_compliance_policy(), but this is fragile and doesn't do exactly what we want it to do.)
X25519 can be disabled via the API, but upstream BoringSSL doesn't have a good way to disable ChaCha20Poly1305, which we want to do in some contexts. (This is currently implemented with setting an obsolete compliance policy via
set_compliance_policy(), but this is fragile and doesn't do exactly what we want it to do.)