Difference between revisions of "Sslmode=require"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
For backwards compatibility with earlier versions of PostgreSQL, if a root CA file exists, the behavior of sslmode=require will be the same as that of verify-ca, meaning the server certificate is validated against the CA. Relying on this behavior is discouraged, and applications that need certificate validation should always use verify-ca or verify-full. | For backwards compatibility with earlier versions of PostgreSQL, if a root CA file exists, the behavior of sslmode=require will be the same as that of verify-ca, meaning the server certificate is validated against the CA. Relying on this behavior is discouraged, and applications that need certificate validation should always use verify-ca or verify-full. | ||
| − | {{psql}} | + | |
| + | == See also == | ||
| + | * {{psql}} | ||
| + | |||
| + | [[Category:psql]] | ||
Revision as of 06:57, 17 February 2023
https://www.postgresql.org/docs/current/libpq-ssl.html
For backwards compatibility with earlier versions of PostgreSQL, if a root CA file exists, the behavior of sslmode=require will be the same as that of verify-ca, meaning the server certificate is validated against the CA. Relying on this behavior is discouraged, and applications that need certificate validation should always use verify-ca or verify-full.
See also
Advertising:
