如何测试某些访客的 SSL 证书是否失败

发布于 2024-11-01 16:20:43 字数 122 浏览 1 评论 0原文

对于我的一些网站访问者来说,SSL 证书失败了。无论我在各种浏览器上进行什么测试,SSL 证书都是有效的。

我想不出如何在客户端进行测试并找出问题。
你会怎么做?

一名客户收到:致命证书未知

For some of my site visitors, the SSL certificate is failing. Whatever tests I do on various browsers for me the SSL certificate is valid.

I can't think of how to test this on client side, and to identify the problem.
How would you do this?

One client gets: fatal certificate unknown

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

风吹短裙飘 2024-11-08 16:20:43

虽然 RouMao 的答案大部分是正确的,但他忽略了 SSL 证书最常见的问题(IME) - 您使用的证书需要来自 CA 的临时证书,而您尚未将其包含在证书链中。大多数 CA 提供用于分析证书的在线工具 - 尝试位于此处的工具。

另外,与使用的浏览器有任何关联吗?值得注意的是,Chrome默认情况下不处理 SSL v2

While RouMao's answer is mostly correct, he has missed what is (IME) the most common problem with SSL certificates - the certificate you are using requires an interim certificate from the CA which you have not included in your certificate chain. Most CAs provide an online tool for analysing the certificate - try the one located here.

Also, is there any correlation with which browser being used? Notably, Chrome does not handle SSL v2 by default

短叹 2024-11-08 16:20:43

大多数 SSL 证书失败都是由访问者自己造成的。不知何故无法通过服务器实现进行测试或验证。

以下是一些明显的示例:

  1. 您的证书自 2012 年 4 月 1 日起生效,但客户端的本地计算机时间设置为 2010 年——比当前时间晚一年。在这种情况下,访问者应该一直遇到问题,直到他的机器时间晚于 2012 年 4 月 1 日。
  2. 访问者位于受限制的防火墙后面。防火墙可以终止 SSL/TLS 连接并使用伪/自签名证书重新加密链接。事实上,这可以被视为中间人附加。
  3. 受信任的根证书被客户自己删除了,

很难解决所有这些问题。有时,您需要创建一个客户端本机应用程序来检测或修复所有可能的问题,并要求客户端浏览器每次进入 HTTPS 模式之前都执行该应用程序。

PS 大多数电子银行应用程序都是这样做的。

Most of the failing of SSL certificates were caused by visitors themselves. Somehow could not tests or verified by server implementation.

Here are some obvious examples:

  1. Your cert is validated since April 1st 2012, but the client's local machine time is set to 2010 -- one year later than current time. In this case, the visitor should encounter problem all the times, until his machine time is later than April 1st 2012.
  2. visitor is behind a restricted firewall. The firewall could terminate the SSL/TLS connection and re-crypt the link with a pseudo/self-sign certificate. Indeed this could be considered as a man-in-middle attach.
  3. The Trusted Root Certification was removed by client himself

it is very hard to fix all these problem. Sometimes, you need to create a client side native application to detect or fix all the possible problems, and require client browser to execute the application each time before it enter the HTTPS mode.

P.S. most of the e-bank application do like this.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文