大网数据广告活动
服务器运维问答

Chrome marks StartCom cert invalid for wildcard part

· 52CE 我爱测

My StartCom cert has CN=opencpu.org and alt names for *.opencpu.org as well as *.ocpu.io . However after the latest chrome update, Chrome marks the SSL cert as valid for the first site, but not the second. Why is this? Does Chrom…

问题原文

原帖链接 · Jeroen Ooms · CC BY-SA 3.0

My StartCom cert has CN=opencpu.org and alt names for *.opencpu.org as well as *.ocpu.io.

However after the latest chrome update, Chrome marks the SSL cert as valid for the first site, but not the second. Why is this? Does Chrome no longer allow multiple wildcards on a single cert?

已采纳解答

原帖链接 · Esa Jokinen · CC BY-SA 3.0

It's a bit tricky to see in Chrome what is causing the problem, as the View certificate button has been hidden inside Menu (three dots) > More tools... > Developer tools > Tab: Security.

There, you could have seen that the error wasn't SSL_ERROR_BAD_CERT_DOMAIN as it would have been, if there was a problem in recognizing the wildcard inside Subject Alternative Name / DNS Name. As a result, Chrome still has support for multiple wildcards on a single cert.

The error was probably SSL_ERROR_UNKNOWN_CA_ALERT as Google removed support for StartCom certificates in Chrome 56 released in January 2017, while the current stable main version is 57. Mozilla Security Group made the same decision at the same time in Firefox 51. If you had your certificate working earlier, you were already using a discontinued version of your browser and skipped at least one main version in your updates.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-04-08)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。