Google switching Chrome to its homemade BoringSSL to make its browser safer


Google has exhausted a lot of resources patching up OpenSSL, so much in fact, the company has elected to create its own fork aptly named BoringSSL. Preparing to move the platform to Chrome, Mountain View recently worked this new implementation into its latest Chromium build. As indicated by its name, OpenSSL is an open source software used for secure connections. Several security holes in OpenSSL recently led to the now infamous Heartbleed scare that worked a large portion of the world into a frenzy.

So far there are over 70 patches for OpenSSL alone and with no signs of slowing down, Google decided to create its own solution to make its products safer. The company says it’s not trying to abolish OpenSSL and notes that it will continue sending bug fixes to its community. Although BoringSSL isn’t completely baked into Google’s browser just yet, it’ll likely be available to test in one of Chrome’s various pre-production builds sometime in the near future.

(via Google)

FTC: We use income earning auto affiliate links. More.

You’re reading 9to5Google — experts who break news about Google and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow 9to5Google on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel