mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-07 13:59:28 +02:00
If the client is compiled with GSSAPI support and tries to start up GSS with the server, but the server is not compiled with GSSAPI support, we would mistakenly end up falling through to call ProcessStartupPacket with secure_done = true, but the client might then try to perform SSL, which the backend wouldn't understand and we'd end up failing the connection with: FATAL: unsupported frontend protocol 1234.5679: server supports 2.0 to 3.0 Fix by arranging to track ssl_done independently from gss_done, instead of trying to use the same boolean for both. Author: Andrew Gierth Discussion: https://postgr.es/m/87h82kzwqn.fsf@news-spur.riddles.org.uk Backpatch: 12-, where GSSAPI encryption was added. |
||
---|---|---|
.. | ||
autovacuum.c | ||
bgworker.c | ||
bgwriter.c | ||
checkpointer.c | ||
fork_process.c | ||
interrupt.c | ||
Makefile | ||
pgarch.c | ||
pgstat.c | ||
postmaster.c | ||
startup.c | ||
syslogger.c | ||
walwriter.c |