commit | 97227dc52d9e6620c8b83eb1dd4d45edf51d9d7f | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Sep 26 20:56:38 2016 -0400 |
committer | Adam Langley <agl@google.com> | Tue Oct 04 01:37:31 2016 +0000 |
tree | f4b3ad6aab9bb58c22fe2d3b29d5471838bcc686 | |
parent | 3e9e043229c529f09590b7074ba062e0094e9821 [diff] |
Replace keywrap AEADs with upstream's APIs. This finally removes the last Android hack. Both Chromium and Android end up needing this thing (Chromium needs it for WebCrypto but currently uses the EVP_AEAD version and Android needs it by way of wpa_supplicant). On the Android side, the alternative is we finish upstream's NEED_INTERNAL_AES_WRAP patch, but then it just uses its own key-wrap implementation. This seems a little silly, considering we have a version of key-wrap under a different API anyway. It also doesn't make much sense to leave the EVP_AEAD API around if we don't want people to use it and Chromium's the only consumer. Remove it and I'll switch Chromium to the new---er, old--- APIs next roll. Change-Id: I23a89cda25bddb6ac1033e4cd408165f393d1e6c Reviewed-on: https://boringssl-review.googlesource.com/11410 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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.
There are other files in this directory which might be helpful: