Google Tightens Security with BoringSSL

  • Thread starter Thread starter Guest
  • Start date Start date
Status
Not open for further replies.
Sounds like some one in Google is trying to sabotage this project.

"The project may have to reject more than it accepts; by Langley's own admission, many of Google's fixes have stability issues."
Also they named it BoringSSL.

I can only think of one company that loathes Android ...
 
This needs to stay OpenSSL so the code can be inspected as one. If Google tries to fork it then two standards have to be maintained. I rather see Google lend a hand in cleaning up the issues with OpenSSL than forking it.
 
Status
Not open for further replies.