pg.ddx.io  pgsql-general@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gustavsson Mikael <mikael.gustavsson@smhi.se>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Cc: Svensson Peter <peter.svensson@smhi.se>
Subject: Re: SV: SV: SV: SV: Problem with ssl and psql in Postgresql 13
Date: Wed, 23 Dec 2020 11:28:21 -0500
Message-ID: <723586.1608740901@sss.pgh.pa.us> (raw)
In-Reply-To: <de4dc5a4f22d43a28300bccb70d99db6@smhi.se>
References: <e5b0b6ed05764324a2f3fe7acfc766d5@smhi.se>
	<20201217.172938.170511532557914014.horikyota.ntt@gmail.com>
	<06191eae74d045e192a786a84a73ba53@smhi.se>
	<65644.1608214801@sss.pgh.pa.us>
	<a748b98ff0a94fe0a1ca54872ec5a25e@smhi.se>
	<CABUevEz0tuQzXYmgDGDsbhs+8V-WOp2cSpM1S70S5L+gSDRGUg@mail.gmail.com>
	<a9e6ef756df24fba948b5c09b1f30229@smhi.se>
	<CABUevEz_eHh=R6C_C7GChF8w_aG4pMPDAvjJFa92cspAb3SSkg@mail.gmail.com>
	<698125e1105644adaa27578bb37b18f6@smhi.se>
	<89909.1608222331@sss.pgh.pa.us>
	<61e2a65bbc2f47d297a6f3cdac2cc6cc@smhi.se>
	<d3ab9042bce34aae85d323d69e3ee430@smhi.se>
	<169637.1608321770@sss.pgh.pa.us>
	<c347c62b507743ceac0aaebd0ccff533@smhi.se>
	<de4dc5a4f22d43a28300bccb70d99db6@smhi.se>

Gustavsson Mikael <mikael.gustavsson@smhi.se> writes:
> I did a final test before logging out for Christmas because i found a thread in hackers discussing some issue with GSS and SSL.
> So if i set gssencmode=disable on my pgsql-13 to postgres 13 server connection i get an SSL connection.

Oooh ... that's the missing ingredient.  Do you have a GSS credentials
cache on the client side, but no support on the server side?

It looks like, if there is a credentials cache and gssencmode isn't
explicitly disabled, we try GSS first.  If the server refuses that:

                    if (gss_ok == 'N')
                    {
                        /* Server doesn't want GSSAPI; fall back if we can */
                        if (conn->gssencmode[0] == 'r')
                        {
                            appendPQExpBufferStr(&conn->errorMessage,
                                                 libpq_gettext("server doesn't support GSSAPI encryption, but it was required\n"));
                            goto error_return;
                        }

                        conn->try_gss = false;
                        conn->status = CONNECTION_MADE;
                        return PGRES_POLLING_WRITING;
                    }

that is, it decides the connection it has is good enough.  This
is not OK if SSL should have been used.

			regards, tom lane





view thread (4+ messages)  latest in thread

Message-ID: <723586.1608740901@sss.pgh.pa.us>
Permalink:  ../723586.1608740901@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/723586.1608740901@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mikael.gustavsson@smhi.se, sfrost@snowman.net, magnus@hagander.net, horikyota.ntt@gmail.com, peter.svensson@smhi.se
  Subject: Re: SV: SV: SV: SV: Problem with ssl and psql in Postgresql 13
  In-Reply-To: <723586.1608740901@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox