Skip to content

BoringSSL - Implement bad certificate callback for client SecureSocket connection #23561

@whesse

Description

@whesse

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.

Metadata

Metadata

Assignees

Labels

P2A bug or feature request we're likely to work onarea-core-librarySDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.library-io

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions