71c21b4300
When writing tests and BoGo isn't available, it is useful to be able to configure the set of signature algorithms accepted on the verify side. Add an API for this. Change-Id: Ic873189da7f8853e412acd68614df9d9a872a0c8 Reviewed-on: https://boringssl-review.googlesource.com/15125 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
---|---|---|
.. | ||
cert_corpus | ||
client_corpus | ||
client_corpus_no_fuzzer_mode | ||
pkcs8_corpus | ||
privkey_corpus | ||
read_pem_corpus | ||
server_corpus | ||
server_corpus_no_fuzzer_mode | ||
session_corpus | ||
spki_corpus | ||
ssl_ctx_api_corpus | ||
cert.cc | ||
client.cc | ||
CMakeLists.txt | ||
minimise_corpuses.sh | ||
pkcs8.cc | ||
privkey.cc | ||
read_pem.cc | ||
refresh_ssl_corpora.sh | ||
server.cc | ||
session.cc | ||
spki.cc | ||
ssl_ctx_api.cc |