Bug 921117

Summary: genkey fails to generate a certificate because the signature is not secure
Product: [Fedora] Fedora Reporter: L.L.Robinson <junk>
Component: crypto-utilsAssignee: Joe Orton <jorton>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: andreincx, _deepfire, emaldona, fidelleon, green, james.faulkner, jl-icase, jorton, jsullivan3, mhlavink, moonwolf, mrleightonbrown, paradoxe
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: crypto-utils-2.4.1-46.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-24 07:45:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description L.L.Robinson 2013-03-13 13:55:20 UTC
Description of problem:
when trying to generate a self signed certificate with genkey --days 365 host.domain.com it fails with the error 

Version-Release number of selected component (if applicable):
(null): bad certificate request
: The certificate was signed using a signature algorithm that is disabled because it is not secure.


How reproducible:every time


Steps to Reproduce:
1.install crypto-utils and mod_ssl
2.run genkey --days 365 demo.example.com
3.say no to generatig a csr
4.input cert data
  
Actual results:
genkey exits with (null): bad certificate request
: The certificate was signed using a signature algorithm that is disabled because it is not secure.


Expected results:genkey to sign it with a secure algorithm and generate a cert


Additional info:

Comment 1 Marcin Trendota 2013-03-19 09:19:01 UTC
Same for F17.

Comment 2 Gendre Sébastien 2013-04-30 19:23:40 UTC
Same problem in F18 with domaine name as argument.

Comment 3 josip@icase.edu 2013-05-19 12:38:29 UTC
Same for F17, using genkey from crypto-utils-2.4.1-39.fc17.x86_64 (currently the latest).

Comment 4 Elio Maldonado Batiz 2013-05-19 17:40:53 UTC
This is caused by a change that came when we updated to nss 3.14 from upstream.
Support for certificate signatures using the MD5 hash algorithm is now disabled by default. - https://developer.mozilla.org/en-US/docs/NSS/NSS_3.14_release_notes
NSS always gives the user a way for the user to override changes for compatibility. Setting a runtime environment variable via NSS_HASH_ALG_SUPPORT=+MD5 should solve your problem. 

This a temporary and longer term genkey should use a more secure digest algorithm. In my opinion you shouldn't have to go around overriding default's. Our tools should do the right thing for you. The burden is on me.

Comment 5 L.L.Robinson 2013-06-14 13:58:37 UTC
I've confirmed that running "export NSS_HASH_ALG_SUPPORT=+MD5" before genkey means the cert can be generated.

Comment 6 Andrei Cosma 2013-07-24 15:52:56 UTC
(In reply to junk from comment #5)
> I've confirmed that running "export NSS_HASH_ALG_SUPPORT=+MD5" before genkey
> means the cert can be generated.

For me it's not working (Fedora 19). I get same error w/o NSS_HASH_ALG_SUPPORT.

Linux skipper 3.9.9-302.fc19.x86_64 #1 SMP Sat Jul 6 13:41:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Comment 7 Samium Gromoff 2013-08-15 09:05:08 UTC
Same for F19

Comment 8 Elio Maldonado Batiz 2013-08-17 15:59:12 UTC
What if in addition to export NSS_HASH_ALG_SUPPORT=+MD5 you also set  
export NSS_ALLOW_WEAK_SIGNATURE_ALG=1, does it work then?

Comment 9 John F Sullivan 2013-09-24 20:59:37 UTC
Same behavior with Fedora 20 Alpha.

crypto-utils-2.4.1-44.fc20.x86_64

Comment 10 Leighton Brown 2013-11-12 04:37:14 UTC
I was able to create a self signed cert on F19 when both settings were applied.

Comment 11 L.L.Robinson 2014-01-10 12:14:27 UTC
Default config still fails in Fedora 20. It's also worth noting that overriding the disabling of the MD5 digest algorithm creates a certificate which many browsers will not trust at all which renders this tool pretty useless.

Comment 14 Fedora Update System 2014-01-22 15:25:19 UTC
crypto-utils-2.4.1-45.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/crypto-utils-2.4.1-45.fc20

Comment 16 Fedora Update System 2014-01-22 15:49:31 UTC
crypto-utils-2.4.1-45.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/crypto-utils-2.4.1-45.fc19

Comment 17 Joe Orton 2014-01-23 09:16:57 UTC
*** Bug 1017960 has been marked as a duplicate of this bug. ***

Comment 18 Fedora Update System 2014-01-23 11:14:24 UTC
Package crypto-utils-2.4.1-46.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing crypto-utils-2.4.1-46.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1390/crypto-utils-2.4.1-46.fc19
then log in and leave karma (feedback).

Comment 19 Fedora Update System 2014-01-24 07:45:33 UTC
crypto-utils-2.4.1-46.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 20 Fedora Update System 2014-02-05 03:37:33 UTC
crypto-utils-2.4.1-48.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.