由于iOS证书验证失败，安全websocket连接在BoringSSL上失败

Question

由于以下iOS错误(12 & 13)，我无法连接到安全的websocket连接。

似乎在验证终结点的证书时失败了，但是我找不到确定原因的方法。我可以从浏览器客户端连接到websocket端点.我还使用https://www.ssllabs.com/ssltest/验证了证书，没有发现任何问题。SSL证书是从“让我们加密”发出的。

下面是我可以从mac笔记本电脑上的设备和控制台应用程序中捕捉到的控制台输出：

XCODE调试控制台

2020-04-29 16:18:03.501170-0700 [BoringSSL] boringssl_context_handle_fatal_alert(1873) [C12.1:1][0x1151122e0] write alert, level: fatal, description: certificate unknown 
2020-04-29 16:18:03.501366-0700 [BoringSSL] boringssl_context_error_print(1863) boringssl ctx 0x282eb41b0: 4450062232:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-283.102.1/ssl/handshake.cc:369: 
2020-04-29 16:18:03.510648-0700 [BoringSSL] boringssl_session_handshake_incomplete(164) [C12.1:1][0x1151122e0] SSL library error 
2020-04-29 16:18:03.510740-0700 [BoringSSL] boringssl_session_handshake_error_print(111) [C12.1:1][0x1151122e0] 4450062232:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-283.102.1/ssl/handshake.cc:369: 
2020-04-29 16:18:03.510837-0700 [BoringSSL] nw_protocol_boringssl_handshake_negotiate_proceed(726) [C12.1:1][0x1151122e0] handshake failed at state 12288 
2020-04-29 16:18:03.532541-0700 [strings] ERROR: Network.NWError not found in table Error of bundle CFBundle 0x109308b40 </System/Library/Frameworks/CoreFoundation.framework> (framework, loaded) 
 error: Optional("The operation couldn’t be completed. (NETWORK.NWERROR error 2.)")

MAC控制台应用程序

default 16:18:03.712414-0700    boringssl_session_handshake_incomplete(170) [C12.1:1][0x1151122e0] Handshake incomplete: waiting for data to read [2]
default 16:18:03.712477-0700    boringssl_session_handshake_incomplete(170) [C12.1:1][0x1151122e0] Handshake incomplete: waiting for data to read [2]
default 16:18:03.712583-0700    boringssl_session_handshake_incomplete(170) [C12.1:1][0x1151122e0] Handshake incomplete: waiting for data to read [2]
default 16:18:03.712646-0700    boringssl_session_handshake_incomplete(170) [C12.1:1][0x1151122e0] Handshake incomplete: waiting for data to read [2]
default 16:18:03.712707-0700    boringssl_context_message_handler(2258) [C12.1:1][0x1151122e0] Reading SSL3_RT_HANDSHAKE 122 bytes
default 16:18:03.713628-0700    boringssl_context_info_handler(1983) [C12.1:1][0x1151122e0] Client handshake state: TLS 1.3 client read_hello_retry_request
default 16:18:03.713687-0700    boringssl_context_add_handshake_message_pending(578) [C12.1:1][0x1151122e0] Adding message(2)
default 16:18:03.713747-0700    boringssl_context_message_handler(2258) [C12.1:1][0x1151122e0] Writing SSL3_RT_CHANGE_CIPHER_SPEC 1 bytes
default 16:18:03.713807-0700    boringssl_context_info_handler(1983) [C12.1:1][0x1151122e0] Client handshake state: TLS 1.3 client read_server_hello
default 16:18:03.713865-0700    boringssl_context_info_handler(1983) [C12.1:1][0x1151122e0] Client handshake state: TLS 1.3 client read_encrypted_extensions
default 16:18:03.714153-0700    boringssl_context_message_handler(2258) [C12.1:1][0x1151122e0] Reading SSL3_RT_HANDSHAKE 10 bytes
default 16:18:03.714219-0700    boringssl_context_info_handler(1983) [C12.1:1][0x1151122e0] Client handshake state: TLS 1.3 client read_certificate_request
default 16:18:03.714277-0700    boringssl_context_message_handler(2258) [C12.1:1][0x1151122e0] Reading SSL3_RT_HANDSHAKE 3105 bytes
default 16:18:03.714335-0700    boringssl_context_info_handler(1983) [C12.1:1][0x1151122e0] Client handshake state: TLS 1.3 client read_server_certificate
default 16:18:03.714395-0700    boringssl_context_info_handler(1983) [C12.1:1][0x1151122e0] Client handshake state: TLS 1.3 client read_server_certificate_verify
default 16:18:03.714452-0700    boringssl_context_message_handler(2258) [C12.1:1][0x1151122e0] Reading SSL3_RT_HANDSHAKE 264 bytes
default 16:18:03.714628-0700    boringssl_context_copy_peer_sct_list(1003) [C12.1:1][0x1151122e0] SSL_get0_signed_cert_timestamp_list returned no SCT extension data
default 16:18:03.714914-0700    boringssl_helper_create_sec_trust_with_certificates(607) [C12.1:1][0x1151122e0] SecTrustCreateWithCertificates result: 0
default 16:18:03.714973-0700    boringssl_helper_create_sec_trust_with_certificates(612) [C12.1:1][0x1151122e0] SecTrustSetOCSPResponse result: 0
default 16:18:03.715033-0700    boringssl_helper_create_sec_trust_with_certificates(621) [C12.1:1][0x1151122e0] No TLS-provided SCTs
default 16:18:03.715167-0700    boringssl_context_certificate_verify_callback(2071) [C12.1:1][0x1151122e0] Asyncing for verify block
default 16:18:03.715225-0700    boringssl_session_handshake_incomplete(170) [C12.1:1][0x1151122e0] Handshake incomplete: certificate evaluation result pending [16]
default 16:18:03.715418-0700    boringssl_context_certificate_verify_callback(2040) [C12.1:1][0x1151122e0] Verification already in progress.
default 16:18:03.715481-0700    boringssl_session_handshake_incomplete(170) [C12.1:1][0x1151122e0] Handshake incomplete: certificate evaluation result pending [16]
default 16:18:03.716084-0700    boringssl_context_certificate_verify_callback(2040) [C12.1:1][0x1151122e0] Verification already in progress.
default 16:18:03.716145-0700    boringssl_session_handshake_incomplete(170) [C12.1:1][0x1151122e0] Handshake incomplete: certificate evaluation result pending [16]
default 16:19:16.180121-0700    boringssl_context_message_handler(2258) [C6.1:2][0x11321ccb0] Writing SSL3_RT_ALERT 2 bytes
default 16:19:16.180202-0700    boringssl_context_handle_warning_alert(1893) [C6.1:2][0x11321ccb0] write alert, level: warning, description: close notify
default 16:19:16.180285-0700    boringssl_session_disconnect(504) [C6.1:2][0x11321ccb0] SSL_shutdown 0
default 16:19:16.181104-0700    nw_protocol_boringssl_remove_input_handler(1012) [C6.1:2][0x11321ccb0] nw_protocol_boringssl_remove_input_handler forced true
default 16:19:16.181169-0700    nw_protocol_boringssl_remove_input_handler(1030) [C6.1:2][0x11321ccb0] Transferring nw_protocol_boringssl_t handle back into ARC for autorelease
default 16:19:33.510159-0700    boringssl_context_message_handler(2258) [C8.1:2][0x11328fd50] Writing SSL3_RT_ALERT 2 bytes
default 16:19:33.510247-0700    boringssl_context_handle_warning_alert(1893) [C8.1:2][0x11328fd50] write alert, level: warning, description: close notify
default 16:19:33.510309-0700    boringssl_session_disconnect(504) [C8.1:2][0x11328fd50] SSL_shutdown 0
default 16:19:33.510922-0700    nw_protocol_boringssl_remove_input_handler(1012) [C8.1:2][0x11328fd50] nw_protocol_boringssl_remove_input_handler forced true
default 16:19:33.511105-0700    nw_protocol_boringssl_remove_input_handler(1030) [C8.1:2][0x11328fd50] Transferring nw_protocol_boringssl_t handle back into ARC for autorelease

端点的NGINX服务器块是：

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name me.example.com;

    ssl_certificate /etc/letsencrypt/live/me.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/me.example.com/privkey.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/me.example.com/chain.pem;

    location /ws {
        proxy_pass http://upstreamserver;

        proxy_http_version  1.1;
        proxy_set_header    Upgrade $http_upgrade;
        proxy_set_header    Connection $connection_upgrade;
        proxy_set_header    Host $host;
        proxy_set_header    X-Real-IP $remote_addr;
        proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header    X-Forwarded-Protocol $scheme;
    }
}

对于为什么这是iOS上的一个问题有什么想法吗？我还在苹果的Dev论坛上发布了这个

Answer 1

问题是LetsEncrypt和NGINX安装程序颁发的SSL证书中出现了错误配置。由于苹果的证书透明度政策的存在，现在iOS上的证书验证更加严格。在Apple论坛上获得了一个很好的答案，它帮助跟踪问题到以下几个方面：

1. LetsEncrypt颁发的证书缺少嵌入式签名证书时间戳(SCT)。我不得不用"OCSP必须订书机“支持重新创建我的证书： certbot --nginx --hsts --主食-ocsp--必经的-d domain.example.com 要验证为证书创建了嵌入式SCT，您可以运行openssl x509 -in cert.pem -text，并且输出应该包含类似的内容： 证书:数据: X509v3扩展:权威信息访问: OCSP：http://ocsp.int-x3.letsencrypt.org CA发行者- URI:http://cert.int-x3.letsencrypt.org/ X509v3证书策略:策略: 2.23.140.1.2.1策略: 1.3.6SCTs:签名证书时间戳:版本: v1 (0x0)日志ID：.1.4.1.44947.1.1.17A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58时间戳:5月1日21:02:14.817 GMT扩展:无签名:ecdsa-with 256 30:45:02:20:2F:2C:22:85:50:DD：FD:DA:62:E9:60:BA: 95:6C:49:03:1E:9E:F9:6C:9F:AA:A0:17:65:7F:D7:D3: A4:E7:CC:02:02:21:00:D4:2F:55:CF:F6:57:AC:BF:3E：E5:8B:F5:A2:00:47:2D:C4:5E:A4:10:EE:D7:D6:B4:FF: 9E:21:1D:CC:6A:89:53签名证书时间戳:版本: v1 (0x0)日志ID : 07:B7:5C:1B:E5:7D:68:FF:F1：B0:C6:1D:23:15:C7:BA: E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C时间戳:521:02:14.843 GMT扩展:无签名: ecdsa-with-SHA256 25630:44:02:20:17:63:1D:8E:76:CA:E0:A2:5C:42:92:7C: BC:06:60:C7:9B:46:BB:59:63:8F:E1:8A:BE:52:CB:15: FD:C4:DE:09:02:20:28:EF:48:E1:4B:BD:9D:05:29:52: FC:D9:5A:8B:82:08:9D:1A:A0:58:F0:33:FB:05:5E:E7: 56:A0:AE:64:84:C7
2. NGINX服务器块需要适当的OCSP配置，删除HTTP/2支持，并使用具有中间证书和嵌入式SCT的证书链 map $http_upgrade $connection_upgrade {默认升级；“关闭；}上游ws-信号{服务器本地主机:8080；}服务器{侦听443 ssl；侦听：：443 ssl；server_name domain.example.com；由Certbot ssl_certificate_key /etc/letsencrypt/live/domain.example.com/privkey.pem；管理的ssl_certificate $http_upgrade##由Certbot # OCSP固定ssl_stapling on；ssl_stapling_verify on；ssl_trusted_certificate /ws解析器8.8.8.8 8.8.4.4；位置/ws{ proxy_pass http://ws-signal；proxy_http_version 1.1；proxy_set_header升级$http_upgrade；proxy_set_header连接$connection_upgrade；proxy_set_header主机$host；}

我还必须将红蜘蛛升级到4.0.3版本。这个最新版本将URLSessionWebSocketTask用于iOS 13+，而iOS 12似乎正在覆盖验证，以便在禁用证书钉扎时返回true。仍然需要尝试与证书钉扎启用，以了解发生了什么。

Answer 2

我刚刚编写了一个类来帮助解决套接字和新的apple TLS限制(参见我的自述)。您很可能错误配置您的证书。除了处理套接字的助手类之外，我还试图布局如何创建符合新的iOS TLS限制的证书。

https://github.com/eamonwhiter73/IOSObjCWebSockets