We recently switched Google’s 2b line repository over to BoringSSL, our fork of OpenSSL. This means that BoringSSL is now powering Chromium (on nearly all platforms), Android M and Google’s production services. For the first time, the majority of Google’s products are sharing a single TLS stack and making changes no longer involves several days of work juggling patch files across multiple repositories. This is a big positive for Google and I’m going to document some of the changes that we’ve made in BoringSSL in this post.

• Uncategorized