aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-05-21 20:41:55 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2015-05-21 20:41:55 -0400
commitc6b7b9a9cef1253ad12122959d0e78f62d8aee1f (patch)
treeffd882e35bd110db060435a25577772c01bb2d73 /src/backend/access/gist/gistproc.c
parent70f2e3e20ff7dd10d2b405764f4818b11f167925 (diff)
downloadpostgresql-c6b7b9a9cef1253ad12122959d0e78f62d8aee1f.tar.gz
postgresql-c6b7b9a9cef1253ad12122959d0e78f62d8aee1f.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/gistproc.c')
0 files changed, 0 insertions, 0 deletions