[tooling] Upgrade psycopg, fix legacy ssl tests #1110
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
the-glu
force-pushed
the
upgrade_psycopg
branch
from
9a41a1e to
64bb01c
Compare
mickmis
approved these changes
Aug 14, 2025
Contributor
Author
|
#1094 has been merged while it contained the commits present in this PR. PR is now useless ^^' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This upgrade psycopg and rewrite
legacy_ssl_version_rejectedto work with any python version.Python / openssl / etc. don't support TLS < 1.2 anymore, so
legacy_ssl_version_rejectedmanually send TLS packets to try to establish an old TLS connection and check for legacy version alerts.This has the same behavior as before (and raw packets on the TCP connection are the same as before).
Follow #1109