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.

Bug 1221442

Summary: Secure connection failed (sec_error_bad_der) due to certs with SAN dNSName entries incorrectly containing IP addresses
Product: Red Hat Enterprise Linux 7 Reporter: Scott Dodson <sdodson>
Component: firefoxAssignee: Martin Stransky <stransky>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: akostadi
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-23 06:28:57 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 Scott Dodson 2015-05-14 03:09:40 UTC 
Description of problem:
Certificates that contain a SAN with "DNS: ipv4address" generate sec_error_bad_der errors in Firefox 38 (and 37).

See https://bugzilla.mozilla.org/show_bug.cgi?id=1148766
Comment 3 Martin Stransky 2015-05-18 18:04:22 UTC 
Kai, your idea here? Should we patch it when upstream patch get r+?
Comment 4 Kai Engert (:kaie) (inactive account) 2015-05-26 12:33:59 UTC 
Depends on the patch that upstream will use.
We should look at the patch when it's available.

Does anyone have a test site for this issue?

Does Firefox offer to override and connect anyway?

(In my opinion, if the certificate is out of spec, we shouldn't allow it by default, but it should be possible to override.)
Comment 5 Scott Dodson 2015-05-26 13:05:34 UTC 
No, there's no ability to bypass the check without going into about:config and whitelisting it.
Comment 6 Kai Engert (:kaie) (inactive account) 2015-05-26 13:45:41 UTC 
(In reply to Scott Dodson from comment #5)
> No, there's no ability to bypass the check without going into about:config
> and whitelisting it.

Which setting in about:config are you using to whitelist?
Comment 7 Scott Dodson 2015-05-26 14:20:17 UTC 
Sorry, I confused two different issues, there appears to be no way to whitelist it.
Comment 11 Aleksandar Kostadinov 2015-09-02 18:45:46 UTC 
FYI the firefox issue has been closed WONTFIX. They list some other alternative to keep certificate correct and still working on windwos:
https://bugzilla.mozilla.org/show_bug.cgi?id=1148766

So I guess we better adapt.
Comment 12 Martin Stransky 2019-08-23 06:28:57 UTC 
Sorry we don't have a fix for that.