wbrawner/openssl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
19257 commits 20 branches 302 tags 153 MiB
Commit graph

7 commits

Author SHA1 Message Date
Matt Caswell
185c29b14e test_sslcbcpadding only makes sense <TLS1.3 
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>
 2016-11-07 15:52:33 +00:00
Matt Caswell
837e591d42 Enable TLSProxy to talk TLS1.3 
Now that ossltest knows about a TLS1.3 cipher we can now do TLS1.3 in
TLSProxy

Reviewed-by: Rich Salz <rsalz@openssl.org>
 2016-11-02 13:28:21 +00:00
David Benjamin
243ecf19dd Add missing parameter. 
Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
 2016-09-26 23:10:29 +01:00
David Benjamin
f3ea8d7708 Switch back to assuming TLS 1.2. 
The TLSProxy::Record->new call hard-codes a version, like
70-test_sslrecords.t.

Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
 2016-09-26 23:10:29 +01:00
David Benjamin
3058b74266 Address review comments. 
Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
 2016-09-26 23:10:29 +01:00
David Benjamin
5cf6d7c51f Don't test quite so many of them. 
Avoid making the CI blow up.

Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
 2016-09-26 23:10:29 +01:00
David Benjamin
8523288e6d Test CBC mode padding. 
This is a regression test for
https://github.com/openssl/openssl/pull/1431. It tests a
maximally-padded record with each possible invalid offset.

This required fixing a bug in Message.pm where the client sending a
fatal alert followed by close_notify was still treated as success.

Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
 2016-09-26 23:10:29 +01:00