Re: Allow peer/ident to fall back to md5?

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: Allow peer/ident to fall back to md5?
Date: 2014-10-29 16:36:42
Message-ID: 5451179A.3030300@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/29/14, 11:23 AM, Josh Berkus wrote:
> I don't see a problem with having a "continue" directive, and
> documenting that it only works with peer and ident. Maybe someday
> (protocol bump) we can have a way to make other methods continue, and
> then nobody will need to change their files to support the new way.

Keep in mind that makes it far easier to accidentally screw up your hba.conf by putting a line in the wrong place. Anyone that's dealt with firewall rules (or apparently PAM) would probably be OK, but a lot of our users would end up with a config that's not doing what they wanted.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeremy Harris 2014-10-29 16:38:44 Re: Directory/File Access Permissions for COPY and Generic File Access Functions
Previous Message Adam Brightwell 2014-10-29 16:36:40 Re: Directory/File Access Permissions for COPY and Generic File Access Functions