https://boringssl.googlesource.com/boringssl/+/HEAD/PORTING.md Looking at the porting section many routines have changed compared to OpenSSL. I can't imagine this fork to become a complete replacement of OpenSSL, but it may be worth considering an integration in Postgres code depending on the features it will have (Curve25519, Ed25519 mentioned). Also since 9.4 the SSL code paths have been rearranged to allow more implementations to be done with other SSL libraries.
Quote:
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don’t recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
