Google started working on their own version of cryptographic library, dubbed BoringSSL, that relies on OpenSSL code but seeks to be more appropriate for their products.
In order to adapt the cryptographic functions of the library to their solutions, Google uses a number of patches on top of OpenSSL; but maintaining them across multiple code bases has become more difficult, to the point that it is more feasible to add modifications from the main code into a forked version rather than keeping O…
Comments are closed.
