Bug 1309780 - gnutls tools should not use SHA1 by default when generating digital signatures/certificates
gnutls tools should not use SHA1 by default when generating digital signature...
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnutls (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Nikos Mavrogiannopoulos
BaseOS QE Security Team
Depends On:
Blocks: 1309777
  Show dependency treegraph
Reported: 2016-02-18 11:42 EST by Nikos Mavrogiannopoulos
Modified: 2016-02-19 03:24 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1309779
Last Closed: 2016-02-18 11:59:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nikos Mavrogiannopoulos 2016-02-18 11:42:14 EST
Description of problem:
SHA1 was published in 1993 and is still in wide use today. However there are several weaknesses and the algorithms is considered today cryptographically broken (less effort than brute force is required). It is highly likely we will have collision attacks in the near future; i.e., forged certificates. For that it is recommended for our tools which deal with digital signatures to no longer use the SHA1 as a hash function by default.

For maximum compatibility with old software we recommend the SHA2-256 algorithm to be used as the default replacement.

As such, it is recommended for all of the included in gnutls tools and shipped configuration files, to switch from SHA1 to SHA2-256 when generating certificates or digital signatures.
Comment 2 Nikos Mavrogiannopoulos 2016-02-18 11:59:19 EST
certtool --generate-privkey --outfile key
certtool --generate-self-signed --load-privkey key --outfile cert
certtool -i --infile cert|grep Signature 
Signature Algorithm: RSA-SHA256

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