BoringSSL - Implement bad certificate callback for client SecureSocket connection #23561
Labels
area-core-library
SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.
library-io
P2
A bug or feature request we're likely to work on
Test: standalone/io/https_bad_certificate_test
Implement the onBadCertificate optional argument to SecureSocket.connect() and SecureSocket.secure(), so that a client that gets an unverifiable certificate from the server can call a programmer-provided callback to decide whether to continue the secure connection attempt, or to close the
connection.
The text was updated successfully, but these errors were encountered: