RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When a GnuTLS client uses TLSv1.2, servers which respect client preference for signature methods will select SHA-1 signature for Server Key Exchange message.

Version-Release number of selected component (if applicable):
gnutls-2.8.5-19.el6_7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. tcpdump -i any -s 0 -w capture.pcap -u port 443
2. gnutls-cli --port 443 --priority NORMAL:+VERS-TLS1.2 bugzilla.redhat.com
3. open capture.pcap in wireshark

Actual results:
Client Hello message contains signautre_alorithms extension with following pairs:
SHA1-RSA
SHA1-DSA
SHA256-RSA
SHA384-RSA
SHA512-RSA

The Server Key Exchange message is signed with SHA1-RSA

Expected results:
Extension containing the signature algorithms in following order:
SHA256-RSA
SHA384-RSA
SHA512-RSA
SHA1-RSA
SHA1-DSA

Server Key Exchange signed with SHA256-RSA

Additional info:
This should also affect server side, at the very least when the %SERVER_PRECEDENCE setting is used.

Verified that this is addressed by the 2.12.x rebase.

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://rhn.redhat.com/errata/RHSA-2017-0574.html