Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Query cancel and OOB data

From: Tom Ivar Helbekkmo <tih+mail(at)Hamartun(dot)Priv(dot)NO>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, byronn(at)insightdist(dot)com, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Query cancel and OOB data
Date: 1998-05-25 05:30:35
Message-ID: 86soly5344.fsf@barsoom.Hamartun.Priv.NO (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:

> OK, lets review this, with thought about our various authentication
> options:
> 	trust, password, ident, crypt, krb4, krb5
> As far as I know, they all transmit queries and results as clear text
> across the network.  They encrypt the passwords and tickets, but not the
> data.  [Even kerberos does not encrypt the data stream, does it?]

True.  Encrypted communication should be an option, though.  With
Kerberos, the ability to do this securely is already there in the
library, so it would be natural to use it.  Adding encryption to the
communication between client and postmaster is probably a good thing
even if we don't (yet) encrypt that between client and backend, and
would also be a good, simple way to start implementing it.

Popularity is the hallmark of mediocrity.  --Niles Crane, "Frasier"

In response to

pgsql-hackers by date

Next:From: Alessandro BaldoniDate: 1998-05-25 07:51:59
Subject: Large objects and locking mechanism
Previous:From: Oliver ElphickDate: 1998-05-25 04:33:23
Subject: Use of password/crypt authentication

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group