| Summary: | dev-db/postgresql-server should support kerberos | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | schmitt953 |
| Component: | [OLD] Server | Assignee: | PgSQL Bugs <pgsql-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | PATCH |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
This is the diff of the 2 ebuilds
9.1.4-r1 with kerberos use flag ebuild patch with postgres-base use flag forced |
||
Created attachment 319140 [details]
9.1.4-r1 with kerberos use flag
This is postgresql-server9.4.1-r1 with a kerberos use flag that enables krb5 and gssapi support. We could separate the two since krb5 is depricated in favor of gssapi.
Noticed a mistake. I should have had it require postgresql-base with use flag kerberos when the kerberos use flag is set for postgresql-server. Created attachment 319144 [details, diff]
ebuild patch with postgres-base use flag forced
This patch is the correct version. It will also force postgresql-base to have the correct use flag.
Comment on attachment 319138 [details, diff]
This is the diff of the 2 ebuilds
It should set a dependency on a Kerberos implementation, too.
(Also, please post unified diffs next time.)
*postgresql-server-9.2.3 (08 Feb 2013) *postgresql-server-9.1.8 (08 Feb 2013) *postgresql-server-9.0.12 (08 Feb 2013) *postgresql-server-8.4.16 (08 Feb 2013) *postgresql-server-8.3.23 (08 Feb 2013) 08 Feb 2013; Aaron W. Swenson <titanofold@gentoo.org> +postgresql-server-8.3.23.ebuild, +postgresql-server-8.4.16.ebuild, +postgresql-server-9.0.12.ebuild, +postgresql-server-9.1.8.ebuild, +postgresql-server-9.2.3.ebuild, postgresql-server-9999.ebuild: Added kerberos USE flag. (Bug 427948) Use python-single-r1.eclass to build PL/Python against the Python of the users choosing. (Bug 427954) 'use' instead of 'need' logger in /etc/init.d/postgresql-${SLOT}. (Bug 435280) Default to sane character encoding default with --encoding=UTF-8 in /etc/conf.d/postgresql-${SLOT}. (Bug 440258) Append ${SLOT} to PAM service name; each slot now has its own PAM service file. (Bug 443113) Security bump. (Bug 456080) |
Created attachment 319138 [details, diff] This is the diff of the 2 ebuilds postgresql-base has a kerberos use flag which enables gssapi however postgresql-server does not. If the user builds postgresql-server and then builds postgresql-base again with the use flag postgres will not recognize gssapi authentication when the server is started and thus the server will refuse to start. If postgresql-server is rebuilt after postgresql-base has its use flags changed it will work however emerge-uDN will not call for this. What I've done is added a kerberos use flag to postgresql-server. I have a patch for postgresql-server-9.1.4-r1. It should also work for postgresql-server-9.1.4 and I will try that soon.