]> 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:32:15 +0000 (10:32 +0100)
commita97efb83d9109eee1aa9770515557dbac2d737d0
tree8ed086af152c22041e6f4edacec2cd3142164241
parent795343e55216d4e75d865663d60c6f62c3fb289f
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: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Neil Horman <nhorman@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/24716)

(cherry picked from commit 214c724e00d594c3eecf4b740ee7af772f0ee04a)
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