X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id A6F449DCA22; Sun, 5 Feb 2006 11:50:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37185-01; Sun, 5 Feb 2006 11:51:00 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from ns.snowman.net (ns.snowman.net [66.92.160.21]) by postgresql.org (Postfix) with ESMTP id 7E29F9DCA17; Sun, 5 Feb 2006 11:50:53 -0400 (AST) Received: by ns.snowman.net (Postfix, from userid 1000) id E1ECD17BA6; Sun, 5 Feb 2006 10:51:56 -0500 (EST) Date: Sun, 5 Feb 2006 10:51:56 -0500 From: Stephen Frost To: Magnus Hagander Cc: Mohan Anon , pgsql-hackers@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [HACKERS] Postgres 8.1.x and MIT Kerberos 5 Message-ID: <20060205155156.GA4474@ns.snowman.net> Mail-Followup-To: Magnus Hagander , Mohan Anon , pgsql-hackers@postgresql.org, pgsql-admin@postgresql.org References: <6BCB9D8A16AC4241919521715F4D8BCE92EA3A@algol.sollentuna.se> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4NxgPrvSrIDR5b4" Content-Disposition: inline In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE92EA3A@algol.sollentuna.se> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 10:48:36 up 239 days, 7:58, 14 users, load average: 0.13, 0.16, 0.08 User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.115 required=5 tests=[AWL=0.115] X-Spam-Score: 0.115 X-Spam-Level: X-Archive-Number: 200602/43 X-Sequence-Number: 20464 --T4NxgPrvSrIDR5b4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Magnus Hagander (mha@sollentuna.net) wrote: > The *REALM* is not checked, however. This can cause problems if you have > a multi-realm system (where the realms already trust each other, because > the KDC has to give out the service ticket) where you have the same > username existing in multiple realms representing different users.=20 This brings up the issue again that it'd be nice to be able to have what amounts to a '.k5login' in PostgreSQL somehow. Ideally, this would be something an idividual user could set up but at good first step would be to have something along the lines of pg_ident.conf for Kerberos connections where the admin could implement a mapping. We should probably also have a configurable option to check the realm or to not check the realm. I'd like to look into doing this for 8.2 but, as usual, I'm not sure I'll have time. Anyone else looking into this? Thanks, Stephen --T4NxgPrvSrIDR5b4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD5h8crzgMPqB3kigRAno0AJ9fPuxoCfRjdDMkSLU1BkXx7dCDPACdGGpP FncY7+UKtX7KY1xd8LyKhsA= =g43Z -----END PGP SIGNATURE----- --T4NxgPrvSrIDR5b4--