From: | George Woodring <george(dot)woodring(at)iglass(dot)net> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Can I disable sslcert/sslkey in pg_service.conf? |
Date: | 2018-06-14 19:06:32 |
Message-ID: | CACi+J=S0aLKyo266K6w3r=4uPXnkzYH3t1gO0XXHDrZHQ+9o+A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
We currently use pg_service.conf and certificates to log into our
databases. Users have their own ~/.postgresql/postgresql.[crt|key] and
everything is happy.
We are testing a cloud based postgres which is requiring password based
authentication, however our existing certificates are causing the cloud
server to reject SSL connections.
[woodring(at)ibeam]$ psql -U woodring -h host1 "dbname=mydb sslmode=require"
psql: SSL error: tlsv1 alert unknown ca
I can make it work from the command line:
[woodring(at)ibeam]$ psql -U woodring -h host1 "dbname=mydb sslmode=require
sslcert= sslkey="
Password for user woodring:
psql (9.5.13, server 9.6.3)
WARNING: psql major version 9.5, server major version 9.6.
Some psql features might not work.
SSL connection (protocol: TLSv1.2, cipher: DHE-RSA-AES256-GCM-SHA384, bits:
256, compression: off)
Type "help" for help.
mydb=> \q
If I put the blanks into pg_service.conf:
[mydb]
dbname=mydb
host=host1
sslmode=require
sslcert=
sslkey=
It does not work.
[woodring(at)ibeam]$ PGSERVICE=mydb psql
psql: SSL error: tlsv1 alert unknown ca
I tried the opposite of moving the .postgresql directory to a different
name and putting a hard coded certificate path in pg_service, but it looks
to have its own sets of challenges.
Thanks for any suggestions.
George Woodring
iGLASS Networks
www.iglass.net
From | Date | Subject | |
---|---|---|---|
Next Message | Data Ace | 2018-06-14 21:33:54 | PostgreSQL Volume Question |
Previous Message | Pierre Timmermans | 2018-06-14 18:00:39 | Re: Database connection log |