Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
This is probably a feature request more than a bug. I'm having to get new SHA256 signed SSL certs for all my servers and noticed the genkey script seems to default to using SHA1 signatures on the CSR. Is there some way to force it to use an SHA256 signature? Tried --sha256 but it wasn't recognized.
Some of the CAs I've dealt with insist I have to have a CSR with SHA256 signature to get an SHA256 cert. I believe this is incorrect and other CAs seem to agree but it would make life easier if the CSR had an SHA256 sig so I wouldn't have argue the issue with the CAs at all.
Is there some way to manually generate the CSR (without using genkey) that will get me an SHA256 sig?
Version-Release number of selected component (if applicable):
all (tried several versions)
How reproducible:
always
Steps to Reproduce:
1. generate a CSR according to RHEL docs
2. check whether signature is SHA1 or SHA256
3.
Actual results:
SHA1 signature
Expected results:
SHA256 would be nice
Additional info:
Steve - thanks for the bug report. Yes, we have fixed this in Fedora to adjust to SHA-256 by default (and -384/-512 for bigger key sizes) - we should be able to bring that fix across.
If this is/was a problem for you in production please could you file a ticket with Red Hat Support as well? It helps us to prioritize requests internally.
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/RHBA-2016-0866.html