← Knowledge base

BoringSSL

BoringSSL is an application TLS library. Embedding applications choose their build and TLS configuration; another BoringSSL-based product’s behavior is not a guarantee for yours.

Evidence to collect

1. Record the application build and pinned BoringSSL revision.
2. Review the application’s configured named groups and provider integration.
3. Use that application’s handshake evidence where possible; a separate OpenSSL check measures the server with a different client.

Record the scope and result

Record the tested component, client, peer, protocol, selected algorithm, and date. Keep observed negotiation, documented capability, and unknown distinct. A failed check can reflect local tooling, certificate validation, network policy, or configuration; it does not prove that all PQC is unsupported.

Official references

• BoringSSL project documentation

Guidance reviewed 24 September 2026. Verify documentation for your deployed release; vendor capabilities and defaults change.