test_sslcbcpadding only makes sense <TLS1.3
authorMatt Caswell <matt@openssl.org>
Mon, 7 Nov 2016 14:44:38 +0000 (14:44 +0000)
committerMatt Caswell <matt@openssl.org>
Mon, 7 Nov 2016 15:52:33 +0000 (15:52 +0000)
We may get failures if we run it in TLS1.3, and it makes no sense anyway
so force TLS1.2

Reviewed-by: Rich Salz <rsalz@openssl.org>
test/recipes/70-test_sslcbcpadding.t

index 22825a096d055c6acf778afc505ca7c5e91feecc..8d3d6fc4b9718e304ea525114a634c2c98f79b86 100644 (file)
@@ -48,6 +48,7 @@ ok(TLSProxy::Message->success(), "Maximally-padded record test");
 # Test that invalid padding is rejected.
 foreach my $offset (@test_offsets) {
     $proxy->clear();
+    $proxy->serverflags("-tls1_2");
     $bad_padding_offset = $offset;
     $proxy->start();
     ok(TLSProxy::Message->fail(), "Invalid padding byte $bad_padding_offset");