Re: New behavior with JDBC 42.2.5 - Mailing list pgsql-general

From Ravi Krishna
Subject Re: New behavior with JDBC 42.2.5
Date
Msg-id trinity-33c46c85-c1a1-45d9-8b6b-1ad547c9227a-1537577217218@3c-app-mailcom-lxa09
Whole thread Raw
In response to Re: New behavior with JDBC 42.2.5  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: New behavior with JDBC 42.2.5
List pgsql-general
> First are doing a socket connection or a host connection? Socket 
> connections ignore sslmode.

The URL template of JDBC used by dbeaver is jdbc:postgresql://{host}[:{port}]/[{database}]

From the manual

"The host component is interpreted as described for the parameter host. In particular, a Unix-domain socket connection
ischosen if the host part is either empty or starts with a slash, otherwise a TCP/IP connection is initiated."
 

In our case the host name does not start with a slash.  So I conclude it is using TCP/IP.


> psql postgresql://localhost:5432/test?sslmode=require
> 
> 
> psql postgresql://localhost:5432/test?sslmode=disable

We are using dbeaver, not psql. dbeaver also provides disable option for sslmode.  I set sslmode=disable and it
immediatelyrejected connection with error "SSL Mode off".  
 

So the puzzle is -> in version 42.1.4 when we do not check "Use SSL " button, connection
fails with "SSL Mode off". In that version we check the box "Use SSL" and then in the dropdown
for sslmode, we select sslmode=require. Only then the connection passes.

In version 42.2.5 even if we do not check "Use SSL" it still behaves the same as 
"Use SSL" checked and sslmode=require. 

I was not able to import the security bulletin fully, but am I right in concluding
that JDBC 42.2.5 always turns on sslmode=require unless we explicitly set sslmode=disable.

Thanks for your help.


pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: heads up on large text fields.
Next
From: Andres Freund
Date:
Subject: Re: heads up on large text fields.