diff options
author | Matt Caswell <matt@openssl.org> | 2017-05-25 11:26:18 +0100 |
---|---|---|
committer | Matt Caswell <matt@openssl.org> | 2017-05-25 15:38:22 +0100 |
commit | 10a1ec4833d16b15964bfa969b32d3b33534b760 (patch) | |
tree | 94e6e4ffe5548b150281d1e5ab8ff2804e5bf0a8 /test/ossl_shim | |
parent | 47695810b3bea3e83e8bc2266e1672676a189efd (diff) |
Fix BoringSSL alert related test failures
Commit bd990e2535 changed our handling of alerts. Some of the BoringSSl
tests were expecting specific errors to be created if bad alerts were sent.
Those errors have now changed as a result of that commit, so the BoringSSL
test config needs to be updated to match.
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/3549)
Diffstat (limited to 'test/ossl_shim')
-rw-r--r-- | test/ossl_shim/ossl_config.json | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/ossl_shim/ossl_config.json b/test/ossl_shim/ossl_config.json index 50433ed107..26da5f0610 100644 --- a/test/ossl_shim/ossl_config.json +++ b/test/ossl_shim/ossl_config.json @@ -256,7 +256,7 @@ ":UNEXPECTED_RECORD:":"unexpected message", ":TLSV1_ALERT_RECORD_OVERFLOW:":"tlsv1 alert record overflow", ":WRONG_SSL_VERSION:":"no protocols available", - ":BAD_ALERT:":"tlsv1 alert record overflow", + ":BAD_ALERT:":"invalid alert", ":HTTP_REQUEST:":"http request", ":HTTPS_PROXY_REQUEST:":"https proxy request", ":WRONG_CERTIFICATE_TYPE:":"wrong certificate type", |