| commit | 38f621a3667afca1262ce3b9390ef5a23042ff19 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Nov 04 17:16:49 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Nov 06 13:31:02 2022 +0000 |
| tree | 64d1206ac0200c5bed9f4b932df893cef315005c | |
| parent | da663b7ca86d70f7da979f9a48d2238ca5762bdd [diff] |
Add the suite of EC_KEY and EC_POINT serializers. OpenSSL added a bunch of these. oct2priv is a little weird (see https://crbug.com/boringssl/534), but I've made it match OpenSSL and set_private_key for now. But I think we should reduce the state-space a bit. EC_KEY_oct2priv behaves slightly differently from upstream OpenSSL in one way: we reject inputs that aren't exactly the right size. This matches the OpenSSL documentation (the OCTET STRING inside an ECPrivateKey, per spec, is fixed-width), but not OpenSSL's behavior. Update-note: see go/xshow when incorporating this change internally. Change-Id: I33863d773ac4c7f3eabf4ffda157e8250c7fdbd9 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/55066 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
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.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
Project links:
There are other files in this directory which might be helpful: