legacy sigalg disallowed or unsupported #15899
Unanswered
eugenestepanyuk
asked this question in
Help & Questions
Replies: 2 comments
-
We're passing the dialectOptions as-is to the connector so I think they might be able to help you out there; https://github.com/tediousjs/tedious |
Beta Was this translation helpful? Give feedback.
0 replies
-
ok, thanks, I'll contact them |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have an api on nodejs and when I try to connect to the database I get an error: "(node:14320) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
(Use
node --trace-deprecation ...
to show where the warning was created)Failed to connect to ip:port - F8510000:error:0A00014D:SSL routines:tls_process_key_exchange:legacy sigalg disallowed or unsupported:c:\ws\deps\openssl\openssl\ssl\statem\statem_clnt.c:2263:"
My connection:
The connection was initially without encrypt in dialectOptions, I found information on the Internet if you make encrypt: false then the problem may disappear, if I uncomment this line the problem really disappears
The question is, how safe and generally normal is it to do so? Could you suggest other solutions to the error?
upd. this error started to occur after updating nodejs from version 16 to 19
Beta Was this translation helpful? Give feedback.
All reactions