AWS redshift: Python driver sslmode default changed to verify-full
Summary
Documents that the default sslmode is now verify-full (was verify-ca) starting in driver 2.2.0, with behavior notes on hostname mismatch warnings.
Security assessment
Defaulting to verify-full enforces full TLS certificate and hostname verification, improving protection against MITM; this is security-hardening documentation, not a specific vulnerability fix.
Evidence
+ * Default value – verify-full
Diff
diff --git a/redshift/latest/mgmt/python-configuration-options.md b/redshift/latest/mgmt/python-configuration-options.md index d3cb62b..ea4eef2 100644 --- a//redshift/latest/mgmt/python-configuration-options.md +++ b//redshift/latest/mgmt/python-configuration-options.md @@ -700 +700 @@ This parameter is optional. - * Default value – verify-ca + * Default value – verify-full @@ -719,0 +720,2 @@ We recommend using `verify-full` for SSL connections whenever possible. +In driver versions 2.2.0 and later, the default is `verify-full`. In earlier versions, the default was `verify-ca`. If you don't set `sslmode` and the server certificate doesn't match the host name, the driver logs a warning and connects. If you set `sslmode`, the driver enforces the mode that you set. +