用户在我的网站上获得 "website unsafe"
Users get "website unsafe" on my website
我有一个在 IIS Windows 服务器上运行的投资组合网站，如果 matters.But 有些人抱怨他们在浏览 website.I 时得到 "website unsafe" 个人没有得到那个错误，我在其他 diveces 上尝试了该网站，但他们也没有。
可能与 SSL 证书有关？我没有买，但我有一个根据 ssl checker 的自签名证书
.我需要购买受信任的 SSL 证书吗？还是有其他问题？
在我的网站上，我有一个 "Contact us" 页面，其中包含一个网络表单，用户应填写姓名、电子邮件...
编辑：我不知道 post 网站 link 是否可以，如果需要请告诉我。
编辑：Link 到网站 here。
这是自签名证书的普遍问题，因为您网站的访问者或其浏览器无法验证您的服务器的身份。这样做的原因是，没有签署它的证书颁发机构，因此浏览器没有在链接到您的证书的信任链中的（根）证书。
这个自签名证书的问题在post
中得到了很好的解释
The risks are for the client. The point of the SSL server certificate is that it is used by the client to know the server public key, with some level of guarantee that the key indeed belongs to the intended server. The guarantee comes from the CA: the CA is supposed to perform extensive verification of the requester identity before issuing the certificate.
When a client (the user and his Web browser) "accepts" a certificate which has not been issued by one of the CA that the client trusts (the CA which were embedded in Windows by Microsoft), then the risk is that the client is currently talking to a fake server, i.e. is under attack. Note that passive attacks (the attacker observes the data but does not alter it in any way) are thwarted by SSL regardless of whether the CA certificate was issued by a mainstream CA or not.
On a general basis, you do not want to train your users to ignore the scary security warning from the browser, because this makes them vulnerable to such server impersonation attacks (which are not that hard to mount, e.g. with DNS poisoning). On the other hand, if you can confirm, through some other way, that the certificate is genuine that one time, then the browser will remember the certificate and will not show warnings for subsequent visits as long as the same self-signed certificate is used. The newly proposed Convergence PKI is an extension of this principle. Note that this "remembered certificate" holds as long as the certificate is unchanged, so you really want to set the expiry date of your self-signed certificate in the far future (but not beyond 2038 if you want to avoid interoperability issues).
It shall be noted that since a self-signed certificate is not "managed" by a CA, there is no possible revocation. If an attacker steals your private key, you permanently lose, whereas CA-issued certificates still have the theoretical safety net of revocation (a way for the CA to declare that a given certificate is rotten). In practice, current Web browser do not check revocation status anyway.
我有一个在 IIS Windows 服务器上运行的投资组合网站，如果 matters.But 有些人抱怨他们在浏览 website.I 时得到 "website unsafe" 个人没有得到那个错误，我在其他 diveces 上尝试了该网站，但他们也没有。
可能与 SSL 证书有关？我没有买，但我有一个根据 ssl checker 的自签名证书 .我需要购买受信任的 SSL 证书吗？还是有其他问题？
在我的网站上，我有一个 "Contact us" 页面，其中包含一个网络表单，用户应填写姓名、电子邮件...
编辑：我不知道 post 网站 link 是否可以，如果需要请告诉我。
编辑：Link 到网站 here。
这是自签名证书的普遍问题，因为您网站的访问者或其浏览器无法验证您的服务器的身份。这样做的原因是，没有签署它的证书颁发机构，因此浏览器没有在链接到您的证书的信任链中的（根）证书。
这个自签名证书的问题在post
中得到了很好的解释The risks are for the client. The point of the SSL server certificate is that it is used by the client to know the server public key, with some level of guarantee that the key indeed belongs to the intended server. The guarantee comes from the CA: the CA is supposed to perform extensive verification of the requester identity before issuing the certificate.
When a client (the user and his Web browser) "accepts" a certificate which has not been issued by one of the CA that the client trusts (the CA which were embedded in Windows by Microsoft), then the risk is that the client is currently talking to a fake server, i.e. is under attack. Note that passive attacks (the attacker observes the data but does not alter it in any way) are thwarted by SSL regardless of whether the CA certificate was issued by a mainstream CA or not.
On a general basis, you do not want to train your users to ignore the scary security warning from the browser, because this makes them vulnerable to such server impersonation attacks (which are not that hard to mount, e.g. with DNS poisoning). On the other hand, if you can confirm, through some other way, that the certificate is genuine that one time, then the browser will remember the certificate and will not show warnings for subsequent visits as long as the same self-signed certificate is used. The newly proposed Convergence PKI is an extension of this principle. Note that this "remembered certificate" holds as long as the certificate is unchanged, so you really want to set the expiry date of your self-signed certificate in the far future (but not beyond 2038 if you want to avoid interoperability issues).
It shall be noted that since a self-signed certificate is not "managed" by a CA, there is no possible revocation. If an attacker steals your private key, you permanently lose, whereas CA-issued certificates still have the theoretical safety net of revocation (a way for the CA to declare that a given certificate is rotten). In practice, current Web browser do not check revocation status anyway.