iOS:在钥匙串中预安装 SSL 证书 - 以编程方式
我想在用户访问该网站之前在钥匙串中安装/保存证书。 我有一个 HTTPS 服务器,我的应用程序在用户访问 https://mysite 之前对用户进行身份验证。
有没有办法可以通过钥匙串中的 POST 请求安装/保存证书,或者可以将该证书(文件)复制到资源包以将其标记为可信?
I want to install/save a certificate in the keychain before the user visits the site.
I have a HTTPS server, and my app authenticates the user before they go to https://mysite.
Is there a way that I can install/save the certificate via a POST request in the keychain or can I copy that certificate (the file) to the resource bundle to mark it trusted?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
一旦您拥有 der 格式的服务器证书,您可以尝试以下代码:
它将把证书添加到您的应用程序的钥匙串沙箱中,即没有其他应用程序会信任您的证书。
Once you have the server certificate in der format you can try the following code:
It will add the certificate to the keychain sandbox of your application i.e. no other application will trust your cert.
来自: http:// /blog.asolutions.com/2011/02/using-tls-with-self-signed-certificates-or-custom-root-certificates-in-ios/
您有两个可用选项:将服务器的证书添加到钥匙串或手动执行验证。无论您采用哪种方法,您都需要在应用程序中包含 DER 编码的 X.509 公共证书。在下面的示例中,它被命名为“ios-trusted-cert.der”)并用它创建一个 SecCertificateRef。 (如果您的服务器的证书是根证书颁发机构的链的一部分,则您应该安装根证书颁发机构而不是服务器的证书。)
请记住,SecCertificateCreateWithData 遵循内存所有权的创建规则,因此当您不再使用时,必须 CFRelease 它。需要它来避免内存泄漏。
接下来,您可以将证书添加到应用程序的钥匙串中。当您希望 iOS 信任您创建的每个新套接字的证书时,这是合适的。
如果您只想验证您正在创建的套接字的证书,而不验证应用程序中的其他套接字的证书,则可以手动验证您对证书的信任。首先,创建一个套接字(假设您的服务器与客户端在同一台计算机上侦听端口 8443)并在其 ssl 设置中禁用其证书链验证:
然后,当您收到套接字已准备好写入数据的回调时,您可以在向服务器写入任何数据或从服务器读取任何数据之前,应验证对服务器包含的证书的信任。首先 (1),使用您连接的服务器的主机名创建客户端 SSL 策略。主机名包含在服务器的证书中,以验证 DNS 将您定向到的服务器是您信任的服务器。接下来 (2),您从套接字获取实际的服务器证书。如果服务器的证书是证书链的一部分,则可能有多个与服务器关联的证书。当您拥有实际的服务器证书时,您可以 (3) 创建信任对象。信任对象代表信任评估的本地上下文。它隔离单独的信任评估,而钥匙串证书适用于所有受信任的套接字。有了信任对象后,您可以(4)设置锚证书,即您信任的证书。最后(5),您可以评估信任对象并发现服务器是否可信。
From: http://blog.asolutions.com/2011/02/using-tls-with-self-signed-certificates-or-custom-root-certificates-in-ios/
You have two options available: add your server’s certificate to the keychain or perform validation manually. Regardless of your approach, you’ll need to include a DER-encoded X.509 public certificate in your app. In the example below, it is named “ios-trusted-cert.der”) and create a SecCertificateRef with it. (If your server’s certificate is part of a chain to a root certificate authority, you should install the root certificate authority rather than your server’s certificate.)
Remember that SecCertificateCreateWithData follows the create rule of memory ownership, so you must CFRelease it when you no longer need it to avoid memory leaks.
Next, you can add your cert to your app’s keychain. This is appropriate when you want iOS to trust your cert for every new socket you create.
If you only want to verify the cert for the socket you are creating and for no other sockets in your app, you can verify your trust in the cert manually. First, create a socket (assuming your server is listening on port 8443 on the same machine as your client) and disable its certificate chain validation in its ssl settings:
Then, when you receive a callback that your socket is ready to write data, you should verify trust in the certificate your server included before writing any data to or reading any data from the server. First (1), create a client SSL policy with the hostname of the server to which you connected. The hostname is included in the server’s cert to authenticate that the server to which DNS directed you is the server you trust. Next (2), you grab the actual server certificates from the socket. There may be multiple certificates associated with the server if the server’s certificate is part of a certificate chain. When you have the actual server certificates, you can (3) create a trust object. The trust object represents a local context for trust evaluations. It isolates individual trust evaluations whereas the keychain certificates apply to all trusted sockets. After you have a trust object, you can (4) set the anchor certificates, which are the certificates you trust. Finally (5), you can evaluate the trust object and discover whether the server can be trusted.