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 1BC3C9DC86F for ; Mon, 6 Feb 2006 11:50:11 -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 84996-05 for ; Mon, 6 Feb 2006 11:50:15 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.207]) by postgresql.org (Postfix) with ESMTP id 79E2E9DC86B for ; Mon, 6 Feb 2006 11:50:05 -0400 (AST) Received: by xproxy.gmail.com with SMTP id i30so786466wxd for ; Mon, 06 Feb 2006 07:50:10 -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=jSHn7STe9E7ooLTGKouhsa334fPHn0/XP4Gk2ih9e3yg5YsQG1ey6rSrPC2jJGWYrXjVtmdBuuZzMQZ0UyPJbiPedJNF0msROM4G7HNiUNnvmXTNgJ14meGNNaNFX82xJqGjvirKkGUhpMzmnWRC7av9F3vFOdznpDTgnh2ikpg= Received: by 10.70.108.19 with SMTP id g19mr6282134wxc; Mon, 06 Feb 2006 07:50:10 -0800 (PST) Received: by 10.70.69.2 with HTTP; Mon, 6 Feb 2006 07:50:10 -0800 (PST) Message-ID: <655c73580602060750s3667b8aw7784ced234ca826@mail.gmail.com> Date: Mon, 6 Feb 2006 10:50:10 -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: <6BCB9D8A16AC4241919521715F4D8BCE6C7FB6@algol.sollentuna.se> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_34575_24192970.1139241010071" References: <6BCB9D8A16AC4241919521715F4D8BCE6C7FB6@algol.sollentuna.se> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.427 required=5 tests=[AWL=0.426, HTML_MESSAGE=0.001] X-Spam-Score: 0.427 X-Spam-Level: X-Archive-Number: 200602/58 X-Sequence-Number: 20479 ------=_Part_34575_24192970.1139241010071 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks. As far as using TLS, it is good approach. Although, we don't need complete channel encryption for every transaction or query. I am looking at a more granular approach where I can decide depending on the security of information exchange whether to encrypt the channel or not (like using maybe GSSAPI). Is this something that will be considered down the line? Mohan On 2/6/06, Magnus Hagander wrote: > > > 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?). > > Ok. Someone more autoconfy than me will have to say something about 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. > > Ah, that explains me not seeing it. > > If you need protection against mitm and connection security, you should > use TLS. We don't use Kerberos for encryption. > > //Magnus > ------=_Part_34575_24192970.1139241010071 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks.

As far as using TLS, it is good approach. Although, we don't= need complete channel encryption for every transaction or query. I am look= ing at a more granular approach where
I can decide depending on the secu= rity of information exchange whether to encrypt the=20
channel or not (like using maybe GSSAPI). Is this something that will b= e considered down
the line?

Mohan

On 2/6/06, Magnus Hagander <<= a href=3D"mailto:mha@sollentuna.net"> mha@sollentuna.net> wrote:
> Hello Magnus,
>
> Regarding the con= figure 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
> add= ing to LIBS did not work as it (krb5support) library needs
> to come after the other libs (is there a way to control that?).
Ok. Someone more autoconfy than me will have to say something about th= at
:-)


> As far as the security issue with Kerberos, here = is the
> relevant thread
>
> http://mailman.mit.edu/pipermail/ke= rberos/2002-October/002043.
> html
> < http://mailman.mit.edu/pipermail/kerberos/2002-October/002043.html><= br>>
> I am sorry it was in Kerberos mailing list not Postgres.
Ah, that explains me not seeing it.

If you need protection agai= nst mitm and connection security, you should
use TLS.  We don't use Kerberos for encryption.

//Magn= us

------=_Part_34575_24192970.1139241010071--