crypto: add debug info to client emit secureConnect
Currently, when debugging a TLS connection there might be multiple debug
statements client emit secureConnect
for the 'secureConnect' event
when using NODE_DEBUG='tls'
. While it is possible to step through this
with a debugger that is not always the fastest/easiest to do if debugging
remote code.
This commit adds some additional information to the debug statements to make it easier to distinguish where the debug statements are coming from.
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
commit message follows commit guidelines