使用自签名证书保护 websocket [英] Secure websockets with self-signed certificate

问题描述

我想使用安全的 Websocket 来提高成功率.我不需要加密.

I want to use secure Websockets to improve the success rate. I don't need the encryption.

我想在使用带有自签名证书的安全 Websockets (wss://example.com) 时看到警告吗?我使用 Chrome 10 进行了尝试，但没有看到警告，也没有要求我接受证书.它只是工作.

Am I suppose to see a warning when using secure Websockets (wss://example.com) with a self-signed certificate? I tried it with Chrome 10 and I don't see a warning and it doesn't ask me to accept the certificate. It just works.

这是 chrome 中的错误还是预期的行为?我以后可以使用自签名证书吗?

Is this a bug in chrome or the expected behavior? Will I be able to use self-signed certificates in the future?

谢谢

推荐答案

是的，这就是 Chrome 目前的行为，但我不希望它在未来继续成为政策.在 firefox 4 中(如果您在 about:config 中启用 WebSockets)，您将收到有关证书的警告.要批准证书，您可能还必须在浏览器中输入 WebSockets URL(用 https 替换 wss)并首先在那里批准(因为来自 WebSockets 连接的关于自签名证书的警告可能不会让您有机会批准它).

Yep, that's the current behavior of Chrome but I wouldn't expect it to continue to be the policy in the future. In firefox 4 (if you enable WebSockets in about:config) you will get a warning about the certificate. To approve the certificate you may also have to enter the WebSockets URL in the browser (substitute wss with https) and approve it there first (since the warning from the WebSockets connection about the self-signed cert may not give you the opportunity to approve it).

我希望所有浏览器都集中在正确的行为上，即抛出一个允许自签名证书获得批准的警告对话框.

I would expect all browsers to converge on the correct behavior which is to throw up a warning dialog that allows the self-signed certificate to be approved.

这篇关于使用自签名证书保护 websocket的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！