Re: SSL SNI - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: SSL SNI
Date
Msg-id 5df46438-c1b4-161c-4669-f6e6ab6797f0@enterprisedb.com
Whole thread Raw
In response to Re: SSL SNI  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SSL SNI
List pgsql-hackers
On 03.06.21 20:14, Tom Lane wrote:
> I wrote:
>> It looks like the immediate problem can be resolved by just adding
>> a check for conn->pghost not being NULL,
> 
> ... scratch that.  There's another problem here, which is that this
> code should not be looking at conn->pghost AT ALL.  That will do the
> wrong thing with a multi-element host list.  The right thing to be
> looking at is conn->connhost[conn->whichhost].host --- with a test
> to make sure it's not NULL or an empty string.  (I didn't stop to
> study this code close enough to see if it'll ignore an empty
> string without help.)

Patch attached.  Empty host string was handled implicitly by the IP 
detection expression, but I added an explicit check for sanity.  (I 
wasn't actually able to get an empty string to this point, but it's 
clearly better to be prepared for it.)


Attachment

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: Fix dropped object handling in pg_event_trigger_ddl_commands
Next
From: Peter Eisentraut
Date:
Subject: Re: Tid scan improvements