| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: change password_encryption default to scram-sha-256? |
| Date: | 2019-04-08 05:28:16 |
| Message-ID: | 20190408052816.GE2712@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 07, 2019 at 08:23:06PM +0200, David Fetter wrote:
> Great idea! Does it make sense to test all, or at least some
> significant fraction of the connectors listed in
> https://wiki.postgresql.org/wiki/Client_Libraries by default?
This is a more interesting list:
https://wiki.postgresql.org/wiki/List_of_drivers
From what I can see, the major drivers not using directly libpq
support our SASL protocol: JDBC and npgsql. However I can count three
of them which still don't support it: Crystal, pq (Go) and asyncpg.
pq and asyncpg are very popular on github, with at least 3000 stars
each, which is a lot I think. I have also double-checked their source
code and I am seeing no trace of SASL or SCRAM, so it seems to me that
we may want to wait more before switching the default.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-08 05:34:42 | Re: change password_encryption default to scram-sha-256? |
| Previous Message | Tsunakawa, Takayuki | 2019-04-08 05:22:17 | RE: reloption to prevent VACUUM from truncating empty pages at the end of relation |