Google devs: Tearing Chrome away from OpenSSL not that easy

  • 27 July 2014
  • 0 replies
  • 463 views

Userlevel 6

Custom BoringSSL fork not quite a drop-in replacement yet

By Neil McAllister, 25 Jul 2014
 
Google is trying to migrate its Chrome browser away from the buggy OpenSSL cryptography library toward BoringSSL, its homegrown fork, but swapping out the crypto code is proving more difficult than it sounds.
 
Google engineer David Benjamin posted a revision to the Chromium source code version control system this week with a seemingly simple aim: "Switch to BoringSSL." But in his revision notes he observed that this wasn't the first time this particular change has been tried.
 The first time the BoringSSL code was added to the Chromium tree was on July 16, but it was quickly pulled back out again after developers found it broke the build of the WebView component for Android.
 
The next attempt was on July 17, but that one caused problems with WebRTC on Android, so the Chromium code was reverted to its former state again.
 
The third time wasn't a charm, either. The BoringSSL code was added back in on July 18 but was reverted after just a few hours, again because of build issues.
 
Full article
 

0 replies

Be the first to reply!

Reply