Re: Changing gssencmode default in Psycopg - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Changing gssencmode default in Psycopg
Date
Msg-id CAOYmi+nUHd8ztwEHLqvgmVD6v_+5jU4aM64Z14p6dqKphWJySg@mail.gmail.com
Whole thread Raw
In response to Re: Changing gssencmode default in Psycopg  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sat, Aug 23, 2025 at 9:16 AM Andres Freund <andres@anarazel.de> wrote:
> I don't know what the right solution is, but it's really not good that
> something as rarely used as gss encryption causes crashes and performance
> issues for everyone.

This seems as good a time as any to mention that I'd like to
eventually default to `gssencmode=disable sslmode=verify-full`. And to
do that without too much wailing and gnashing of teeth, I'd like to
introduce an /etc config for client-side defaults. I think this would
allow us to make the changes we've really wanted to make for a while,
and then end users can override us if they're certain they don't want
those changes.

I think the sslmode bump will be an easier sell than the gssencmode
drop, though.

On Sat, Aug 23, 2025 at 4:27 AM Daniele Varrazzo
<daniele.varrazzo@gmail.com> wrote:
> Would there be any shortcoming in doing so, apart from obviously
> requiring GSS users to specify prefer/require for the parameter?

I think that's the big one, but it is a big one. Some nonzero fraction
of users will have their security downgraded from passive, low-effort
encryption to absolutely nothing.

--Jacob



pgsql-hackers by date:

Previous
From: Yugo Nagata
Date:
Subject: Re: vacuumdb --missing-stats-only and permission issue
Next
From: jian he
Date:
Subject: Re: Problem in 'ORDER BY' of a column using a created collation?