Google Is Maintaining A "BoringSSL" Fork Of OpenSSL
Written by Michael Larabel in Google on 21 June 2014 at 05:00 AM EDT. Add A Comment
A Google engineer has went public on Google's fork of OpenSSL that is tentatively dubbed BoringSSL.

For years Google has maintained their own set of dozens of patches atop OpenSSL that haven't been upstreamed over breaking API/ABI compatibility, being too experimental, etc. In light of all the OpenSSL fallout this year and wanting to take a different direction in handling their mass amount of out-of-tree patches, Google is no longer basing their work atop OpenSSL upstream but rather will be importing new OpenSSL changes into their code-base.

Google doesn't intend to replace OpenSSL as a project but they will be pulling their new "BoringSSL" work into Chromium and Android. Google will also continue to send bug reports to upstream OpenSSL, continue their existing sponsorships, etc. BoringSSL will also pull in changes from OpenBSD's LibreSSL.

More details on this "BoringSSL" work by Google can be found on Adam Langley's blog.
About The Author
Author picture

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

Related Google News
Popular News
Trending Reviews & Featured Articles