Don't send a status_request extension in a CertificateRequest message
authorMatt Caswell <matt@openssl.org>
Thu, 5 Sep 2019 15:43:57 +0000 (16:43 +0100)
committerMatt Caswell <matt@openssl.org>
Fri, 6 Sep 2019 09:07:11 +0000 (10:07 +0100)
commitdebb64a0ca43969eb3f043aa8895a4faa7f12b6e
treea6a0a771c6bd14b43467a3e76640e45c7bdf67e4
parent7e8c3381937354cf171ceaf4c69315e9a45d4858
Don't send a status_request extension in a CertificateRequest message

If a TLSv1.3 server configured to respond to the status_request extension
also attempted to send a CertificateRequest then it was incorrectly
inserting a non zero length status_request extension into that message.

The TLSv1.3 RFC does allow that extension in that message but it must
always be zero length.

In fact we should not be sending the extension at all in that message
because we don't support it.

Fixes #9767

Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/9780)
ssl/statem/extensions_srvr.c