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 5738F9DC868 for ; Mon, 6 Feb 2006 11:10:33 -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 78033-02 for ; Mon, 6 Feb 2006 11:10:37 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by postgresql.org (Postfix) with ESMTP id 37EDB9DC832 for ; Mon, 6 Feb 2006 11:10:29 -0400 (AST) Received: by xproxy.gmail.com with SMTP id i30so780155wxd for ; Mon, 06 Feb 2006 07:10:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Mi4SbKfcniVo/zOxBJHiGoaI+GJYQZlOzs3gXaNod1mATz/N3hMk4rYFnPJ2E05SiXWWPb+3DeA1zr/Uchp9meNqrRO2+xzmuhL4nLz6d+fXQEKXMjqH+nTRAs1l1GXmNe+Q/YARP8wOqnbU1iZWZEXEHSsAOJoYfQZHuX4Df/s= Received: by 10.70.71.13 with SMTP id t13mr6266838wxa; Mon, 06 Feb 2006 07:10:34 -0800 (PST) Received: by 10.70.69.2 with HTTP; Mon, 6 Feb 2006 07:10:34 -0800 (PST) Message-ID: <655c73580602060710q29517camf200af8cd010d61a@mail.gmail.com> Date: Mon, 6 Feb 2006 10:10:34 -0500 From: Mohan K To: Magnus Hagander Subject: Re: Postgres 8.1.x and MIT Kerberos 5 Cc: pgsql-hackers@postgresql.org, pgsql-admin@postgresql.org In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE92EA3A@algol.sollentuna.se> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_34067_32503003.1139238634642" References: <6BCB9D8A16AC4241919521715F4D8BCE92EA3A@algol.sollentuna.se> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.946 required=5 tests=[HTML_10_20=0.945, HTML_MESSAGE=0.001] X-Spam-Score: 0.946 X-Spam-Level: X-Archive-Number: 200602/56 X-Sequence-Number: 20477 ------=_Part_34067_32503003.1139238634642 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello Magnus, Regarding the configure issue: The platform is Tru64 Unix 5.1b, the problem I had was we have compiled our Kerberos build statically and is installed in a directory other than the standard location. The trick adding to LIBS did not work as it (krb5support) library needs to come after the other libs (is there a way to control that?). As far as the security issue with Kerberos, here is the relevant thread http://mailman.mit.edu/pipermail/kerberos/2002-October/002043.html I am sorry it was in Kerberos mailing list not Postgres. On 2/5/06, Magnus Hagander wrote: > > Greetings, > > I was trying to build source build postgres 8.1.x with MIT > > Kerberos 5 1.4.x implementation. > > The whole thing bombs out. After some digging, I had to hack > > the autoconf script (configure.in) to properly account for > > the way the libraries are built for 1.4.x. I don't know > > whether an earlier post had the same issue. I think it boils > > down to adding the 'libkrb5support' when all the krb5 libs > > are checked in the configure script. > > (This is better asked in -hackers, I htink, copying there) > > What platform is this? I use it with krb5 1.4.3 on Linux (slackware) > without any modifications at all. Perhaps platform specific behaviour? > > The postmaster is linked to libkrb5support, but I only have "-lkrb5" in > my LIBS as generated by configure. However, if I do "ldd" on libkrb5.so > I see that one pulls in libkrb5support. > > > > On another note, is the kerberos authentication secure, I had > > searched some old threads, where it was indicated the > > principal is not checked by the db as a valid user. Is this > > still the case? > > The principal name is definitly checked by the db as a valid user, and > AFAIK it always has been (do you have a reference to where it says it > doesn't?) > > 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. > > If you're in a single realm, it's definitly secure. > > //Magnus > ------=_Part_34067_32503003.1139238634642 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello Magnus,

Regarding the configure issue:
 The platform i= s Tru64 Unix 5.1b, the problem I had was we have
compiled our Kerberos b= uild statically and is installed in a
directory other than the standard= location. The trick adding to LIBS
did not work as it (krb5support) library needs to come after the
oth= er libs (is there a way to control that?).


As far as the securit= y issue with Kerberos, here is the relevant thread

http://mailman.mit.edu/pipermail/kerberos/2002-October/002043.html
<= br>I am sorry it was in Kerberos mailing list not Postgres.


On 2= /5/06, Magnus Hagander <mha@sollen= tuna.net > wrote:
> > Greetings,
> >  I was tryin= g to build source build postgres 8.1.x with MIT
> > Kerberos 5 1.4= .x implementation.
> > The whole thing bombs out. After some diggi= ng, I had to hack
> > the autoconf script (configur= e.in) to properly account for
> > the way the libraries are bu= ilt for 1.4.x. I don't know
> > whether an earlier post had the sa= me issue. I think it boils
> > down to adding the 'libkrb5support' when all the krb5 libs> > are checked in the configure script.
>
> (This is b= etter asked in -hackers, I htink, copying there)
>
> What plat= form is this? I use it with krb5=20 1.4.3 on Linux (slackware)
> without any modifications at all. Perhap= s platform specific behaviour?
>
> The postmaster is linked to= libkrb5support, but I only have "-lkrb5" in
> my LIBS as g= enerated by configure. However, if I do "ldd" on=20 libkrb5.so
> I see that one pulls in libkrb5support.
>
>=
> > On another note, is the kerberos authentication secure, I ha= d
> > searched some old threads, where it was indicated the
> > principal is not checked by the db as a valid user. Is this
&g= t; > still the case?
>
> The principal name is definitly ch= ecked by the db as a valid user, and
> AFAIK it always has been (do y= ou have a reference to where it says it
> doesn't?)
>
> The *REALM* is not checked, however. Th= is can cause problems if you have
> a multi-realm system (where the r= ealms 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.=
>
> If you're in a single realm, it's definitly secure.
&g= t;
> //Magnus
>
------=_Part_34067_32503003.1139238634642--