仅适用于 API 访问的 ssl 和证书问题
我有一个移动应用程序将通过 https 与我的网络服务器进行通信。我的问题是，我是否需要担心安装证书，因为该 api 的所有流量都是无头的？
据我了解，SSL 为请求提供加密，证书为最终用户建立信任。因为这些对我的网络服务器的调用本质上是无头的，所以我想我不需要担心信任的建立。
我的这个想法正确吗？
I have a mobile app that will be communicating with my webserver over https. My question is, do I even need to worry about installing a certificate since all traffic to this api will be headless?
In my understanding, SSL provides the encryption for a request, and a certificate establishes trust for the end user. Because these calls to my webserver will essentially be headless, I'm thinking I don't need to worry about the trust establishment.
Am I correct in this thinking?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您需要一个自签名证书或CA 签名证书以便使用HTTPS 在您的服务器上。
如果您的证书不是由证书颁发机构分配给您的，那么您进行的任何连接都将 在您必须处理的
URLRequest中触发错误。不受信任的证书的问题在于恶意中间人< /a> 可以使用他自己的自签名证书在您的服务器之间伪造数据，并可能获取他不应该访问的身份验证凭据或数据。如果您正在处理任何身份验证凭据或其他私人数据，我建议您仅请求签名证书。如果您货比三家，您可以找到每年 10-20 美元的廉价签名证书，这对于保护您的用户来说是一笔微不足道的成本。
但是，如果这只是一个个人项目（您唯一需要担心的数据是您的），或者您将发送的任何数据都是免费可用的，则自签名证书可能就足够了。
You will either need a self-signed certificate or a CA-signed certificate in order to use HTTPS on your server.
If your certificate is not assigned to you by a certificate authority, then any connection you make will trigger an error in your
URLRequestthat you will have to handle. The problem with an untrusted certificate is that a malicious man-in-the-middle could fake data to and from your server with his own self-signed certificate, and possibly pick up authentication credentials or data that he should not have access to.If you are dealing with any authentication credentials or other private data, I'd recommend just requesting a signed certificate. If you shop around, you can find cheap signed certificates for $10-20 a year, which is a trivial cost to protect your users.
However, if this is just a personal project (the only data you have to worry about is yours), or any data that you will be sending is freely available, a self-signed certificate may be enough.