new tls.TLSSocket issue

• Version: 10.x+
• Platform: All
• Subsystem: tls

When I try to create a secure connection over an existing stream, implementing something similar to STARTTLS, the suggested way is to use new tls.TLSSocket().

I also want to use mutual certification authentication but the tlsSocket.authorized is never set to true for the Server even when the client certificate is signed correctly by the expected CA. From the _tls_wrap.js code, it seems this flag is only set for the server when the underlying stream is an actual socket.

On the client side things are working as expected, as the client side connection is created with tls.connect().

It used to be that the deprecated pair returned by tls.createSecurePair() has access to the internal SSL object, which I can use verifyError() to check the validity of the client certificate. But this hidden feature has also been removed in recent versions.

What is the correct approach to mca for "upgraded" connection?

从 _tls_wrap.js 以及报告中描述的 TLSSocket 构造路径开始；将其与 tls.connect() 路径和之前 tls.createSecurePair() 的行为进行比较。确认升级后的 stream 如何提供双向证书验证，然后将完成标准定义为一种受支持且可测试的方法，或一种有明确文档说明的限制。