问题原文
原帖链接 · Michael Uray · CC BY-SA 3.0
I assigned a self signed wildcard certificate to an OpenWRT (LEDE) router LUCI (uHTTPd) system. The CA which signed this certificate got added to all browsers as trusted certificate authoritiy.
It works fine on Internet Explorer, Edge and Chrome, but not on Firefox 58.0.2, which throws the error SSL_ERROR_BAD_CERT_DOMAIN, even when it states on the same error page that the certificate is issued for this domain.
If I issue the certificate directly for the host (no wildcard) then it works fine in FF as well.
What could cause this issue?
已采纳解答
原帖链接 · pmhahn · CC BY-SA 4.0
Your certificate has the following "Subject Alternative Names" (SAN):
- DNS:*.mainserver.local
- DNS:*.mainserver
- DNS:*.mgmt.ctb.co.at
- IP:192.168.0.254
- IP:192.168.0.9
- IP:192.168.10.254
- IP:192.168.11.254
- IP:192.168.12.254
- DNS:mgmt.ctb.co.at
- DNS:mainserver.local
Firefox does not like entry 2, as it considers mainserver a TLD and aborts there; the following entries are not checked, so your fw1.mgmt.ctb.co.at never matches entry 3.
I solved a similar problem in our domain be re-ordering the SANs and putting all FQDNs first; you should move your entry 2 to the end.
Firefox issues of interest
- 1489045: Wildcard certificate not working properly using enterprise roots
- 1196364: Proper handling for wildcard certificates for all tlds
- 1757758: consider having mozilla::pkix ignore invalid entries in subjectAlternativeNames
- Public Suffix List
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
