Hi!
Or, if you want to check/enforce this from the server side,
you could enable log_connections and see what's logged;
or simply change pg_hba.conf to disallow non-SSL connections.
I set log_connections =on
pg_hba.conf contains :
local all postgres tru
"Andrus" writes:
> log file does not show ssl connection info:
> 2019-03-22 16:49:03 EET [unknown] [unknown] LOG:
> connection received: host=xx.xx.xx.xx port=54590
> 2019-03-22 16:49:04 EET testuseryle LOG: connection
> authorized: user=testuser databas
On 3/22/19 2:00 AM, Andrus wrote:
Hi!
Old Postgres
"PostgreSQL 9.1.2 on x86_64-unknown-linux-gnu, compiled by gcc-4.4.real
(Debian 4.4.5-8) 4.4.5, 64-bit"
Server has symlinks server.crt and server.key in data directory
/var/lib/postgresql/9.1./main and ssl=true in postgresql.conf file.
S
"Andrus" writes:
> Client accesses server from Windows 10 using psqlODBC driver with
> sslmode=allow in connection string.
> How to verify that connection is encrypted ?
When using libpq directly, you could use PQsslInUse(),
or PQsslAttribute() for more detailed info. I'm not
sure if ODBC provi
