From 3e7cb13dff37795f022a1bedc5951130099a0fc6 Mon Sep 17 00:00:00 2001 From: Matt Caswell Date: Mon, 20 Aug 2018 17:44:58 +0100 Subject: [PATCH] Test that a client protocol "hole" doesn't get detected as a downgrade Reviewed-by: Viktor Dukhovni (Merged from https://github.com/openssl/openssl/pull/7013) --- test/recipes/70-test_tls13downgrade.t | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/test/recipes/70-test_tls13downgrade.t b/test/recipes/70-test_tls13downgrade.t index f7c8812345..b84ca69a8b 100644 --- a/test/recipes/70-test_tls13downgrade.t +++ b/test/recipes/70-test_tls13downgrade.t @@ -45,7 +45,7 @@ use constant { $proxy->filter(\&downgrade_filter); my $testtype = DOWNGRADE_TO_TLS_1_2; $proxy->start() or plan skip_all => "Unable to start up Proxy for tests"; -plan tests => 4; +plan tests => 5; ok(TLSProxy::Message->fail(), "Downgrade TLSv1.3 to TLSv1.2"); #Test 2: Downgrade from TLSv1.3 to TLSv1.1 @@ -73,6 +73,16 @@ ok(TLSProxy::Message->fail() && $alert->description() == TLSProxy::Message::AL_DESC_ILLEGAL_PARAMETER, "Fallback from TLSv1.3"); +SKIP: { + skip "TLSv1.1 disabled", 1 if disabled("tls1_1"); + #Test 5: A protocol "hole" should not be detected as a downgrade + $proxy->clear(); + $proxy->filter(undef); + $proxy->clientflags("-no_tls1_2"); + $proxy->start(); + ok(TLSProxy::Message->success(), "TLSv1.2 protocol hole"); +} + sub downgrade_filter { my $proxy = shift; -- 2.25.1