From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Marisa Emerson <mje(at)insec(dot)sh> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: BSD Authentication support |
Date: | 2016-03-12 02:49:24 |
Message-ID: | 56E383B4.80509@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/7/16 9:40 PM, Marisa Emerson wrote:
> There's a port for PAM, but we would prefer to use BSD Auth as its quite
> a lot cleaner and is standard on OpenBSD.
>
> I've attached an updated patch that includes documentation. It has been
> tested against OpenBSD 5.8. I'll add this thread to the commitfest.
(Not a BSD user, just reviewing the code.)
configure.in has "build with BSD support", which should be "build with
BSD Authentication support".
There should be some documentation of the new configure option in
installation.sgml.
The documentation in client-auth.sgml speaks of a postgresql user and an
auth group. Maybe that's clear to users of BSD, but I don't know
whether these are OS entities or groups that I need to create or what.
The auth_userokay() call hardcodes a "type" of "pg-auth". That seems
important and should probably be documented. Extrapolating from PAM, I
think that should perhaps be an option in pg_hba.conf.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-03-12 02:50:34 | Re: Proposal: BSD Authentication support |
Previous Message | Dilip Kumar | 2016-03-12 02:46:53 | Re: Relation extension scalability |