| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | samay sharma <smilingsamay(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Proposal: Support custom authentication methods using hooks |
| Date: | 2022-03-03 09:30:19 |
| Message-ID: | eacbd52f-07a4-32be-e3df-85ea58f0e373@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02.03.22 21:26, Stephen Frost wrote:
> Part of the point, for my part anyway, of dropping support for plaintext
> transmission would be to remove support for that from libpq, otherwise a
> compromised server could still potentially convince a client to provide
> a plaintext password be sent to it.
I think there should be a generalized feature for client-side selecting
or filtering of authentication methods. As long as there exists more
than one method, there will be tradeoffs and users might want to avoid
one or the other. I don't think removing a method outright is the right
solution for that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-03-03 09:45:42 | Re: Proposal: Support custom authentication methods using hooks |
| Previous Message | Jille Timmermans | 2022-03-03 09:21:05 | Re: Support for grabbing multiple consecutive values with nextval() |