Bug 1388932 - gnutls: interoperability issue 3.3.x vs. 3.5.5
Summary: gnutls: interoperability issue 3.3.x vs. 3.5.5
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnutls
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nikos Mavrogiannopoulos
QA Contact: Hubert Kario
URL:
Whiteboard:
Depends On:
Blocks: 1377248
TreeView+ depends on / blocked
 
Reported: 2016-10-26 13:44 UTC by Nikos Mavrogiannopoulos
Modified: 2017-08-01 08:48 UTC (History)
3 users (show)

Fixed In Version: gnutls-3.3.26-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 08:48:22 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2292 normal SHIPPED_LIVE Moderate: gnutls security, bug fix, and enhancement update 2017-08-01 12:39:15 UTC

Description Nikos Mavrogiannopoulos 2016-10-26 13:44:45 UTC
Description of problem:
Originally reported at:
https://lists.gnupg.org/pipermail/gnutls-devel/2016-October/008209.html

... That said I also reproduced the issue; the fault is with the older
version, as it requires a CertificateStatus message if ServerHello
included the (empty) "status_request" extension, although RFC 6066
explicitly states:

   Note that a server MAY also choose not to send a "CertificateStatus"
   message, even if has received a "status_request" extension in the
   client hello message and has sent a "status_request" extension in the
   server hello message.

So the new gnutls code doesn't do anything wrong by replying with an
empty "status_request" extension, even if there is no chance of sending
a CertificateStatus message, just the old versions can't handle it.

The new version handles this by passing optional = 1 in the call to
_gnutls_recv_handshake(GNUTLS_HANDSHAKE_CERTIFICATE_STATUS) in
status_request.c.

Comment 5 errata-xmlrpc 2017-08-01 08:48:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2292


Note You need to log in before you can comment on or make changes to this bug.