Library:BoringSSL
Appearance
| Developer | |
|---|---|
| License | Apache-2.0 |
| Website | https://boringssl.googlesource.com/boringssl/ |
| On this wiki | Facts · Code · Notes · Topics |
Google's fork of OpenSSL (Apache-2.0, no stable releases) used by Chrome, Android and gRPC; it keeps OpenSSL API names but reports itself as "BoringSSL", has no version number and prints OPENSSL_internal in error strings.
Overview
BoringSSL is a fork of Library:OpenSSL maintained for Google products; it has no release numbers and no ABI promise, so every consumer vendors a specific commit. AWS-LC is a separate fork of it. See Technique:Identifying cryptographic libraries.
Identification
- Version macros:
include/openssl/base.hdefinesOPENSSL_IS_BORINGSSL,OPENSSL_VERSION_NUMBER 0x1010107f(a fixed fake 1.1.1) andBORINGSSL_API_VERSION(an integer that increments with API changes; 44 on main). Fact:BoringSSL/identification/Version macros and OpenSSL_version. - Version string:
OpenSSL_version(OPENSSL_VERSION)returns exactly "BoringSSL" (crypto/crypto.cc); the other queries return placeholders "compiler: n/a", "built on: n/a", "platform: n/a", "OPENSSLDIR: n/a". OPENSSL_VERSION_TEXT in the header is "OpenSSL 1.1.1 (compatible; BoringSSL)". - Error strings: ERR_error_string gives
error:%08x:<library>:OPENSSL_internal:<reason>; the function field is always the literal "OPENSSL_internal" (crypto/err/err.cc). Fact:BoringSSL/string/OPENSSL_internal error format. - Extra exports not in OpenSSL:
BORINGSSL_self_test,BORINGSSL_integrity_test,TLS_with_buffers_method(TLS without crypto/x509; declared in ssl.h),FIPS_mode(returns 0 unless built FIPS). Many legacy OpenSSL APIs are missing.
Code & repositories
- https://github.com/google/boringssl @
594a44291086dcc7cef06cabec4c0b47afd674c0· license: Apache-2.0
BoringSSL source: include/openssl/base.h, crypto.h, crypto/crypto.cc, crypto/err/err.cc.
Tested on: source read, not run: Source read at this commit; not built. · checked 2026-10-18; last activity 2026-10-18
Pitfalls
- Because OPENSSL_VERSION_NUMBER is fake, a binary built against BoringSSL headers is not 1.1.1; do not map its constants to OpenSSL 1.1.1 bug lists.
- AWS-LC (aws/aws-lc commit f3e723d851ec034216c4a3c273c3ad5644249946) answers
OpenSSL_version(OPENSSL_VERSION)with its own string, not an OpenSSL one:crypto/crypto.cline 113 returnsAWSLC_VERSION_STRING, andinclude/openssl/crypto.h(lines 135-137) documents it as "AWS-LC" with the version number appended (AWSLC_VERSION_NUMBER_STRINGis "5.11.0" ininclude/openssl/base.hline 68). The other queries return placeholders ("built on: n/a", "platform: n/a"). The macroOPENSSL_VERSION_TEXTdiffers from the function: it is "OpenSSL 1.1.1 (compatible; AWS-LC 5.11.0)" (crypto.hline 127), so a compiled-in macro string and the runtime string can both be found in one binary. I did not locate the definition ofAWSLC_VERSION_STRINGitself, so the exact runtime text is taken from the header comment.