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:
The UTF-8 characters are stored in the certificates issuer DN of T61STRING and the certificate worked fine in httpd 2.2.x, because httpd 2.2.x uses the byte array in the certificate issuer DN as it is without any conversion. In httpd 2.4.x, Each byte in the DN of T61STRING are converted to UTF-8, as a result, the original UTF-8 characters are garbled. For backward compatibility, an option to disable UTF-8 conversion is needed.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Do you have an example cert and can you explain exactly how this fails?
I'm not sure what you mean by "the original UTF-8", a T.61 string is an 8-bit format which can't store UTF-8. mod_ssl in 2.4 uses OpenSSL's ASN.1 string conversion routines to convert to UTF-8, so I'm surprised if that is failing.
Hi Joe, Thank you for picking up this.
Please find the attached bz1440590.tar.gz and apply it as follows:
1. copy bz1440590.tar.gz to your RHEL6
2. cd /etc/httpd
3. tar zxvf bz1440590.tar.gz
4. cp bz1440590/httpd22/ssl.conf conf.d/
5. service httpd stop
6. service httpd start
7, curl --cacert /etc/httpd/bz1440590/server/cacert.pem --cert /etc/httpd/bz1440590/client/newcert.pem --key /etc/httpd/bz1440590/client/newreq.pem https://localhost:443/
You will get the 200 response.
Then, apply it to your RHEL7 setup as well. You will get the 403 response then. Please give it a try.
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://access.redhat.com/errata/RHBA-2018:0826