summaryrefslogtreecommitdiff
path: root/openssl/include/openssl/x509_vfy.h
diff options
context:
space:
mode:
authoragl@chromium.org <agl@chromium.org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c>2014-07-14 21:22:52 +0000
committeragl@chromium.org <agl@chromium.org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c>2014-07-14 21:22:52 +0000
commitf0c775a4f902aca6abb5d4b1d5ba3260adf73541 (patch)
treeb921b88490afc774058a8b7f8fd07995adf90e77 /openssl/include/openssl/x509_vfy.h
parent063a4b93646788bd883fc0cb1b5eafc991ddacc4 (diff)
downloadopenssl-f0c775a4f902aca6abb5d4b1d5ba3260adf73541.tar.gz
OpenSSL: forward to BoringSSL.
This change will sit in the OpenSSL deps repo. When we switch to BoringSSL, that patch will update DEPS to point to this revision. This avoids having to update webrtc and libjingle repos at the same time. The NaCl build is removed because I believe that all the pointers to it are in the main Chromium repo and can be switched over. I'd rather get a clear build error than linking in both OpenSSL and BoringSSL. (Also, forwarding doesn't appear to work for NaCl targets.) BUG=393317 https://codereview.chromium.org/383273002/ git-svn-id: http://src.chromium.org/svn/trunk/deps/third_party/openssl@283025 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Diffstat (limited to 'openssl/include/openssl/x509_vfy.h')
0 files changed, 0 insertions, 0 deletions