-
Notifications
You must be signed in to change notification settings - Fork 841
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
Feature Request - TLS1.3 Support #5628
Comments
We are still waiting for TLS v1.2 support: No word at all... |
We are waiting for OpenSSL 1.1.1 update on NodeJS followed by migration to the same from our end. nodejs/node#18770 |
I may have missed your questions, can you point me to them? @shamasis openssl 1.1.1a is on current, and on 11.x, and should come out in 10.x in the next LTS release that allows semver-minors, I believe that will be in April 2019. As for TLS1.3 support, see nodejs/node#26209 |
I'm sorry, I didn't notice I'd followed a link out of the nodejs issue tracker and into postman. Please disregard above (unless there is something useful in it). |
We are now in the middle of year 2020 and TLS 1.3 is still not supported. Since our security folks pushed our backend servers to use TLS 1.3 only, we can't use postman for development anymore. I had to return to old deprecated chrome app, which is very sad, because it works... Error: write EPROTO 4816:error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version:c:\users\administrator\buildkite-agent\builds\pm-electron\postman\electron-release\vendor\node\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1407:SSL alert number 70 |
@cache-sk We've added support for TLS 1.3 in Postman app v7.25.2 which will be available for everyone (phased rollout) soon. Till then you can use our Canary app which already supports TLS 1.3. |
@codenirvana That's very good news, thank you! |
Closing this issue. |
Is there a plan to support TLS 1.3?
TLS 1.3 Test: https://tls13.crypto.mozilla.org/
The text was updated successfully, but these errors were encountered: