Re: sslmode=require fallback - Mailing list pgsql-hackers

From Tom Lane
Subject Re: sslmode=require fallback
Date
Msg-id 23855.1468590911@sss.pgh.pa.us
Whole thread Raw
In response to Re: sslmode=require fallback  (Magnus Hagander <magnus@hagander.net>)
Responses Re: sslmode=require fallback  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> The entire "prefer" mode is a design flaw, that we unfortunately picked as
> default mode.
> ...
> If you care about encryption, you should pick something else
> (require/verify). If you don't care about encryption, you should pick
> something else (allow, probably) so as not to pay unnecessary overhead.

Yeah.  The problem with going over to any one of those as the built-in
default is that we can't know whether the user cares about encryption
or not; but all the other choices depend on making that value judgment.
"prefer" is surely an ugly compromise, but nonetheless it often manages
to do the right thing for both camps.

I'm inclined to think that a better answer than changing libpq's behavior
is to encourage DBAs to specify "hostssl" in pg_hba.conf for all external
connections.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Oddity in handling of cached plans for FDW queries
Next
From: Tom Lane
Date:
Subject: Re: Documentation fix for CREATE FUNCTION