BoringSSL

BoringSSL
Software: OpenSSL contributorsScreenshot: VulcanSphere · Apache License 2.0 · source
Name	BoringSSL
Developer	Google
Released	2014
Programming language	C (programming language)
Operating system	Android (operating system), Linux, macOS, Windows
License	BSD-style

BoringSSL

BoringSSL is an open-source fork of OpenSSL created and maintained by Google to provide a smaller, audit-focused, and internally tailored cryptography library for use across Google's products and services. It emphasizes simplicity, removal of legacy APIs, and closer alignment with TLS clients and servers used within large-scale infrastructure such as Chrome (web browser), Android (operating system), and various Cloud computing platforms. The project balances interoperability with major protocols while diverging from upstream projects to meet stringent operational and security requirements.

History

BoringSSL was announced in 2014 as part of a wave of security-focused initiatives following high-profile vulnerabilities like Heartbleed that affected OpenSSL. The fork originated within Google engineering teams to address auditability needs observed in the aftermath of incidents affecting LibreSSL and OpenSSL ecosystems. Initial adoption was driven by integration efforts for Chrome (web browser), replacement of OpenSSL in specific Android (operating system) components, and by teams operating large-scale services on Google Cloud Platform and YouTube. Over time, development has been coordinated through internal Google repositories with selective public releases, reflecting priorities similar to those that shaped other major projects like Chromium and Android Open Source Project.

Design and Features

BoringSSL was designed to remove legacy baggage and provide a streamlined API surface tailored for internal consumers such as Chrome (web browser), Android (operating system), and various server products at Google. It trims rarely used OpenSSL features, deprecates older cipher suites related to protocols like early TLS versions, and focuses on implementing modern primitives such as TLS 1.3 and ChaCha20-Poly1305. The codebase restructures portions of RSA (cryptosystem), Elliptic-curve cryptography, and X.509 certificate handling to simplify integration with projects like Chromium and Android Open Source Project. Platform-specific optimizations target architectures used by Google Pixel devices, Intel, AMD, and ARM servers, drawing on lessons from cryptographic engineering efforts at organizations such as Mozilla and Microsoft.

Security and Auditing

Security posture for the project emphasizes proactive auditing and reduced attack surface, mirroring practices from high-assurance efforts in projects such as LibreSSL and security programs at Google. BoringSSL removes complex, seldom-used code paths to limit vulnerabilities similar to those exposed by Heartbleed. The project participates in coordinated vulnerability disclosure with entities including CERT Coordination Center and implements mitigations against side-channel attacks studied by academic groups at institutions like MIT, Stanford University, and ETH Zurich. Regular code review and fuzzing efforts leverage infrastructure concepts popularized by OSS-Fuzz and continuous-integration workflows from initiatives like Travis CI and Bazel. Security advisories that affect the ecosystem are often cross-referenced with upstream OpenSSL issues and coordinated with browser vendors such as Mozilla and Microsoft.

Usage and Adoption

Adoption has been concentrated among large-scale consumers where customized TLS stacks are beneficial, notably Chrome (web browser), Android (operating system), Google Cloud Platform, and services at YouTube. Other projects and companies have adopted or experimented with the codebase for performance or compliance reasons, including server-side deployments at cloud providers inspired by practices at Amazon Web Services and Microsoft Azure. The code has influenced decisions in the Chromium ecosystem, impacting related projects such as Electron (software framework) and contributing to conversations with standards bodies like the IETF. Third-party adoption is cautious due to API differences from OpenSSL and the maintenance model, but ecosystem projects including cURL and certain nginx builds have explored integrations.

Compatibility and API Changes

A core design decision has been to avoid API compatibility with OpenSSL where such compatibility would perpetuate legacy complexity; as a result, BoringSSL intentionally breaks or omits many OpenSSL APIs. This approach forces callers like Chromium and Android Open Source Project components to use a stable, simplified interface tailored to modern TLS use-cases. The project maintains a minimal, documented surface for X.509 parsing, session management, and cryptographic primitives, while removing APIs for deprecated protocols and cipher suites found in older OpenSSL releases. Compatibility implications have required downstream projects—similar to migration efforts undertaken by LibreSSL adopters—to adapt build systems and code, often aligning with tooling from Bazel and package configurations used in distributions like Debian and Fedora.

Performance and Benchmarks

Performance work has focused on practical throughput and latency improvements for web and mobile clients, borrowing optimization strategies used at Google for YouTube and Google Search infrastructure. Benchmarks typically compare handshake latency, symmetric cipher throughput (including AES-NI acceleration on Intel and AMD), and software fallbacks such as ChaCha20 on ARM devices. Results reported within the community usually highlight competitive performance against OpenSSL in common web scenarios, with particular gains in matrixed environments where simplified code paths reduce CPU usage. Performance tuning interacts closely with compiler toolchains from GCC and Clang (compiler), and deployment profiles often reflect telemetric data gathered from production environments at Google.

Category:Cryptographic libraries