]> git.ipfire.org Git - thirdparty/openssl.git/commit
Add a test for an empty NextProto message
authorMatt Caswell <matt@openssl.org>
Fri, 21 Jun 2024 13:29:26 +0000 (14:29 +0100)
committerMatt Caswell <matt@openssl.org>
Thu, 27 Jun 2024 09:37:54 +0000 (10:37 +0100)
commita201030901de9f9a48b34c38f6922fb0b272f26f
tree42f7c1ae0f4548a03dba3ce33fdd34e3dd29399d
parent0453bf5a7ac60ab01c8bb713d8cc2a94324aa88c
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)
test/recipes/70-test_npn.t [new file with mode: 0644]
util/perl/TLSProxy/Message.pm
util/perl/TLSProxy/NextProto.pm [new file with mode: 0644]
util/perl/TLSProxy/Proxy.pm