Re: SASL, compression? - Mailing list pgsql-hackers

From Neil Conway
Subject Re: SASL, compression?
Date
Msg-id 20020518151853.5e241714.nconway@klamath.dyndns.org
Whole thread Raw
In response to SASL, compression?  (Bear Giles <bgiles@coyotesong.com>)
Responses Re: SASL, compression?  (Bear Giles <bgiles@coyotesong.com>)
List pgsql-hackers
On Sat, 18 May 2002 11:39:51 -0600 (MDT)
"Bear Giles" <bgiles@coyotesong.com> wrote:
> 1) add SASL.  This is a new standards-track protocol that is often
>    described as "PAM" for network authentication.  PostgreSQL could
>    remove *all* protocol-specific authentication code and use
>    standard plug-in libraries instead.

I'm not that clueful about SASL -- would this mean that we could get
rid of the PostgreSQL code that does SSL connections, plus MD5, crypt,
ident, etc. based authentication, and instead just use the SASL stuff?
Or would SSL/TLS support need to co-exist with SASL?

> 2) add ZLIB compression.

This was discussed before, and the conclusion was that compression
is of fairly limited utility, and can be accomplished by using
ssh -- so it's not worth the bloat. But there were some dissenting
opinions at the time, so this might merit further discussion...

> The biggest drawback, at least initially, is that the initial
> exchange will need to be totally rewritten.

I'd like to see a FE/BE protocol change in 7.4, so this might be a
possibility at that point.

Cheers,

Neil

-- 
Neil Conway <neilconway@rogers.com>
PGP Key ID: DB3C29FC


pgsql-hackers by date:

Previous
From: "Joel Burton"
Date:
Subject: Set-returning function syntax
Next
From: Tom Lane
Date:
Subject: Re: Updated CREATE FUNCTION syntax