Re: [PATCH v6] GSSAPI encryption support

On 3/8/16 5:44 PM, Robbie Harwood wrote:

> Here's yet another version of GSSAPI encryption support.

OK, everything seems to be working fine with a 9.6 client and server so
next I tested older clients and I got this error:

$ /usr/lib/postgresql/9.1/bin/psql -h localhost \
-U vagrant(at)PGMASTERS(dot)NET postgres
psql: FATAL: GSSAPI did no provide required flags

There's a small typo in the error message, BTW.

Here's the output from the server logs:

DEBUG: forked new backend, pid=7746 socket=9
DEBUG: postgres child[7746]: starting with (
DEBUG: postgres
DEBUG: )
DEBUG: InitPostgres
DEBUG: my backend ID is 2
DEBUG: StartTransaction
DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR,
xid/subid/cid: 0/1/0, nestlvl: 1, children:
DEBUG: Processing received GSS token of length 667
DEBUG: gss_accept_sec_context major: 0, minor: 0, outlen: 161,
outflags: 1b2
DEBUG: sending GSS response token of length 161
DEBUG: sending GSS token of length 161
FATAL: GSSAPI did no provide required flags
DEBUG: shmem_exit(1): 1 before_shmem_exit callbacks to make
DEBUG: shmem_exit(1): 6 on_shmem_exit callbacks to make
DEBUG: proc_exit(1): 3 callbacks to make
DEBUG: exit(1)
DEBUG: shmem_exit(-1): 0 before_shmem_exit callbacks to make
DEBUG: shmem_exit(-1): 0 on_shmem_exit callbacks to make
DEBUG: proc_exit(-1): 0 callbacks to make
DEBUG: reaping dead processes
DEBUG: server process (PID 7746) exited with exit code 1

I got the same result with a 9.4 client so didn't try any others.

--
-David
david(at)pgmasters(dot)net