MartianH

Ran into the same issue. I was used to having versioning built in from different frameworks. Will this be resolved?

Greetings, Connecting works just fine, it is when i send queries that the problem arise. I should have mentioned that I am using NestJS and I use sequelize for [raw...

>have you try Node 16 with the latest version of Tedious - 14.6.1? Yes. Both 14.6.x and 14.5.x, as mentioned in the ticket. That said `[email protected]` use an older version...

I made a custom script to retrieve a table using `tedious: ^14.6.0`. Code in question (sensitive data omitted): ```js const { Connection, Request } = require('tedious'); const config = {...

Reran aforementioned script with `node --openssl-legacy-provider query.js` as requested. Response is much of the same. ```js Error: ConnectionError: Failed to connect to {server_url} - socket hang up at Connection.socketError ([root_dir_omitted]/node_modules/tedious/lib/connection.js:1425:28)...

Greetings, Apologies for the late response. I will have to discuss this with the team to see what TLS cipher is the issue.

> Tedious logs which cipher is being used for the TLS negotiation through the debug output. Can you add something like this to your custom script and run it using...

> Can you also post the output of `node -p crypto.constants.defaultCoreCipherList | tr ':' '\n'` running against Node 16 and Node 18? Node 16 ```console TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES128-GCM-SHA256...

> `NODE_DEBUG` Node 18 ```console DEBUG:: State change: Initialized -> Connecting (node:5941) Warning: `config.options.trustServerCertificate` will default to false in the future. To silence this message, specify a value explicitly in...

```console DEBUG:: State change: Initialized -> Connecting (node:3100) Warning: `config.options.trustServerCertificate` will default to false in the future. To silence this message, specify a value explicitly in the config options (Use...