diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-05-21 20:41:55 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-05-21 20:41:55 -0400 |
| commit | 2c2c5f0e02b58d225385f5008fb797a90935cb06 (patch) | |
| tree | 1cee4425e0781ed7b7e27e36a8249f592f159652 /src/backend/access/gist/gistold.c | |
| parent | 5b461f239eae2ad67f268e31ada7d79331b89652 (diff) | |
| download | postgresql-2c2c5f0e02b58d225385f5008fb797a90935cb06.tar.gz postgresql-2c2c5f0e02b58d225385f5008fb797a90935cb06.zip | |
Back-patch libpq support for TLS versions beyond v1.
Since 7.3.2, libpq has been coded in such a way that the only SSL protocol
it would allow was TLS v1. That approach is looking increasingly obsolete.
In commit 820f08cabdcbb899 we fixed it to allow TLS >= v1, but did not
back-patch the change at the time, partly out of caution and partly because
the question was confused by a contemporary server-side change to reject
the now-obsolete SSL protocol v3. 9.4 has now been out long enough that
it seems safe to assume the change is OK; hence, back-patch into 9.0-9.3.
(I also chose to back-patch some relevant comments added by commit
326e1d73c476a0b5, but did *not* change the server behavior; hence, pre-9.4
servers will continue to allow SSL v3, even though no remotely modern
client will request it.)
Per gripe from Jan Bilek.
Diffstat (limited to 'src/backend/access/gist/gistold.c')
0 files changed, 0 insertions, 0 deletions