diff options
| author | davidben <davidben@chromium.org> | 2015-04-21 19:36:41 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-04-22 02:36:54 +0000 |
| commit | 2bcbc6bceb6017c762ef01553a55a12fe390de16 (patch) | |
| tree | b44d9b97e521927703b146fc348f9e45096ce603 /win8 | |
| parent | 0c71fc50716dcf2fef839bde83ef09287c64202b (diff) | |
| download | chromium_src-2bcbc6bceb6017c762ef01553a55a12fe390de16.zip chromium_src-2bcbc6bceb6017c762ef01553a55a12fe390de16.tar.gz chromium_src-2bcbc6bceb6017c762ef01553a55a12fe390de16.tar.bz2 | |
Initial support for using BoringSSL with NSS certificates.
This switches the USE_OPENSSL Linux and CrOS builds to continue
setting USE_NSS_CERTS. This lets it use BoringSSL for the crypto
and SSL stack and NSS for certificate verification. See design
doc for details on the flags:
https://docs.google.com/document/d/1x4DOCKwFkAxl9MGfd6snIzFigO4ku6Shuci0r5BzasQ/edit
On Linux, only client auth and OCSP stapling are missing. On ChromeOS,
there are some problematic USE_NSS_CERTS APIs in RSAPrivateKey to
resolve. We also still need to resolve crbug.com/347404 to maintain
parity.
As a follow-up, USE_OPENSSL_CERTS on non-Android can now be
removed (it was never supported anyway).
BUG=462040
Review URL: https://codereview.chromium.org/881213004
Cr-Commit-Position: refs/heads/master@{#326222}
Diffstat (limited to 'win8')
0 files changed, 0 insertions, 0 deletions