You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the deprecation of ssl.wrap_socket, carrying TLS arguments makes little sense and is inappropriately limiting.
Provide an alternative to the ssl* parameters (excluding sslmode) with a single secure parameter. Where secure will provide the entire functionality required by python.socket.SocketFactory.secure. Users will pass the wrap_socket method of the SSLContext they (already) configured as the secure keyword.
Possible separate patch: make this usable with postgresql.open indicators, by adding a security dictionary to postgresql.sys where applications may configure the set of secure functions used. postgresql.open("pq://user@host/database?[security]=tls-context-name")?
The text was updated successfully, but these errors were encountered:
With the deprecation of
ssl.wrap_socket
, carrying TLS arguments makes little sense and is inappropriately limiting.Provide an alternative to the
ssl*
parameters (excludingsslmode
) with a singlesecure
parameter. Wheresecure
will provide the entire functionality required bypython.socket.SocketFactory.secure
. Users will pass thewrap_socket
method of the SSLContext they (already) configured as thesecure
keyword.Possible separate patch: make this usable with
postgresql.open
indicators, by adding asecurity
dictionary topostgresql.sys
where applications may configure the set ofsecure
functions used.postgresql.open("pq://user@host/database?[security]=tls-context-name")
?The text was updated successfully, but these errors were encountered: