pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mohan K <mohan.anon@gmail.com>
To: Magnus Hagander <mha@sollentuna.net>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres 8.1.x and MIT Kerberos 5
Date: Mon, 6 Feb 2006 10:50:10 -0500
Message-ID: <655c73580602060750s3667b8aw7784ced234ca826@mail.gmail.com> (raw)
In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE6C7FB6@algol.sollentuna.se>
References: <6BCB9D8A16AC4241919521715F4D8BCE6C7FB6@algol.sollentuna.se>

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 <mha@sollentuna.net> 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
> > <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
>

view thread (10+ messages)  latest in thread

Message-ID: <655c73580602060750s3667b8aw7784ced234ca826@mail.gmail.com>
Permalink:  ../655c73580602060750s3667b8aw7784ced234ca826@mail.gmail.com/
Also on:    postgresql.org/message-id/655c73580602060750s3667b8aw7784ced234ca826@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mohan.anon@gmail.com, mha@sollentuna.net, pgsql-hackers@postgresql.org
  Subject: Re: Postgres 8.1.x and MIT Kerberos 5
  In-Reply-To: <655c73580602060750s3667b8aw7784ced234ca826@mail.gmail.com>
  References: <6BCB9D8A16AC4241919521715F4D8BCE6C7FB6@algol.sollentuna.se> <655c73580602060750s3667b8aw7784ced234ca826@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox