Red Hat Bugzilla – Bug 1326389
GnuTLS server does not accept SHA-384 and SHA-512 Certificate Verify signatures despite advertising support for them
Last modified: 2017-03-21 05:03:24 EDT
Created attachment 1146506 [details] packet capture for connections with different signatures Description of problem: When using GnuTLS server with client certificates and a client that prefers strong hashes like SHA-512 or SHA-384 will be rejected by server, even though the server advertises support for SHA-384 and SHA-512 in Certificate Request. Version-Release number of selected component (if applicable): gnutls-2.8.5-19.el6_7.x86_64 How reproducible: always Steps to Reproduce: 1. start gnutls server with client certificates 2. connect to it with restrictive client 3. Actual results: Alert(fatal, handshake_failure) Expected results: successful connection Additional info:
Steps to Reproduce: 1. git clone https://github.com/tomato42/tlsfuzzer.git 2. pushd tlsfuzzer 3. git clone https://github.com/warner/python-ecdsa .python-ecdsa 4. ln -s .python-ecdsa/ecdsa ecdsa 5. git clone https://github.com/tomato42/tlslite-ng.git .tlslite-ng 6. ln -s .tlslite-ng/tlslite tlslite 7. popd 8. tar xzf certificates.tar.gz 9. gnutls-serv --priority NORMAL:+VERS-TLS1.2 --port 4433 --http --x509cafile ca/cert.pem --x509keyfile server/key.pem --x509certfile server/cert.pem (in other console, same directory) 10. PYTHONPATH=tlsfuzzer python tlsfuzzer/scripts/test-rsa-sigs-on-certificate-verify.py -k client/key.pem -c client/cert.pem certificates.tar.gz are attachment 1146558 [details]
This is a limitation of that code base; similarly with: https://bugzilla.redhat.com/show_bug.cgi?id=1328205#c1 Will not be addressed.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
there are two solutions to the problem, either implementing support for other hashes or not advertising support for hashes that are not supported. Leaving code as is makes it RFC non compliant.
Of course there are solutions, but they have to be put in perspective. The plan is to address critical TLS 1.2 issues that will affect our use-case, rsyslog. Not to rewrite the best TLS 1.2 implementation out there based on legacy code.
Re-opening as this can be addressed by the server not advertising unsupported hashes on certificate request.
I'm unable to use the reproducer for testing this request. I've verified manually on the 2.12.x rebase, using tcpdump, that the only hashes advertised on a certificate request are the sha1 and sha256 hashes.
yes, I will need to write a new test to expect reply with just two hashes
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