| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Volker Aßmann <volker(dot)assmann(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(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-07 19:00:49 |
| Message-ID: | 20150507190049.GE27644@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 7, 2015 at 11:53:21AM +0200, Volker Aßmann wrote:
> Yes in fact, it would be a way for organizations distributing their own
> PostgreSQL packages to enforce authentication restrictions within the package
> instead of having to educate all users about the options.
>
>
> I don't necessarily agree with the patch as proposed. I would rather
> have a comma-separated list of methods, as in:
>
> --disable-auth=ident,peer
Why don't they just apply a source code patch before compiling?
Configure seems like an odd place for this.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2015-05-07 19:17:04 | commitfest app bug/feature |
| Previous Message | Fabien COELHO | 2015-05-07 18:57:08 | Re: PATCH: pgbench allow '=' in \set |