| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Volker Aßmann <volker(dot)assmann(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Disabling trust/ident authentication configure option |
| Date: | 2015-05-06 22:41:28 |
| Message-ID: | 554A9898.9040407@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/06/2015 02:13 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> (Personally I think there's a very good case for completely ripping out
>> RFC1413 ident auth. I've not seen it used in a great long while, and
>> it's always been a security risk.)
>
> FWIW, I agree with that --- or at least making it a not-built-by-default
> option.
I have seen it in the last year, actually, but only once, which even for
my personal pool represents < 1% usage. So ...
> Probably the right time to make any such changes is at the same time
> we add the proposed more-secure-than-MD5 password option.
+1 to kill off ident when we replace MD5, since users will need to be
beaten over the head about changes to auth methods anyway.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2015-05-06 22:41:34 | Re: Disabling trust/ident authentication configure option |
| Previous Message | Jim Nasby | 2015-05-06 22:32:44 | Re: Disabling trust/ident authentication configure option |