-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to verify certificate/ca from server are valid #397
Comments
Have started work on what will hopefully work to allow this functionality - just needs a bit more work and hopefully some tests around it |
Have submitted a pull request |
tvrprasad
pushed a commit
to tvrprasad/tedious
that referenced
this issue
Sep 11, 2016
This allows accepting or rejecting a connection to a server that presents an untrusted certificate. This fixes tediousjs#397 and tediousjs#399.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With encrypted=true I expect connection to a server with a self-signed certificate to fail due to the CA not being trusted. Connecting though silently accepts the certificates.
Digging through the tls source this looks to be functionality supported by
tls.tlsSocket()
but not bytls.createSecurePair()
tls.createSecurePair()
is deprecated as of node 6.x ( previously reported in #135 ) and so this might be good time to look at migrating over to using tls.tlsSocket as it will allow for connections to reject if unauthorised.This may be considered a duplicate of #282
The text was updated successfully, but these errors were encountered: