openssl/util/perl/TLSProxy
Matt Caswell a201030901 Add a test for an empty NextProto message
It is valid according to the spec for a NextProto message to have no
protocols listed in it. The OpenSSL implementation however does not allow
us to create such a message. In order to check that we work as expected
when communicating with a client that does generate such messages we have
to use a TLSProxy test.

Follow on from CVE-2024-5535

Reviewed-by: Neil Horman <nhorman@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/24718)
2024-06-27 10:37:54 +01:00
..
Alert.pm Remove unnecessary trailing whitespace 2019-02-05 16:25:11 +01:00
Certificate.pm Add a test for correct handling of the cryptopro bug extension 2019-01-07 09:39:10 +00:00
CertificateRequest.pm Teach TLSProxy how to parse CertificateRequest messages 2019-09-06 10:07:11 +01:00
CertificateVerify.pm Following the license change, modify the boilerplates in util/, tools/ 2018-12-06 14:17:23 +01:00
ClientHello.pm Add a test for correct handling of the cryptopro bug extension 2019-01-07 09:39:10 +00:00
EncryptedExtensions.pm Add a test for correct handling of the cryptopro bug extension 2019-01-07 09:39:10 +00:00
Message.pm Add a test for an empty NextProto message 2024-06-27 10:37:54 +01:00
NewSessionTicket.pm Following the license change, modify the boilerplates in util/, tools/ 2018-12-06 14:17:23 +01:00
NextProto.pm Add a test for an empty NextProto message 2024-06-27 10:37:54 +01:00
Proxy.pm Add a test for an empty NextProto message 2024-06-27 10:37:54 +01:00
Record.pm Remove unnecessary trailing whitespace 2019-02-05 16:25:11 +01:00
ServerHello.pm Remove unnecessary trailing whitespace 2019-02-05 16:25:11 +01:00
ServerKeyExchange.pm Remove unnecessary trailing whitespace 2019-02-05 16:25:11 +01:00