Tom Lane wrote:
Bear Giles [EMAIL PROTECTED] writes:
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.
What are the benefits of SASL+Postgresql compared to Postgresql over plain SSL?
Coz Postgresql already supports SSL right?
Cheerio,
Link.
At 03:11 PM 5/18/02 -0600, Bear Giles wrote:
If it's being used in Sendmail, Cyrus IMAP and OpenLDAP, with preliminary
work (sponsored by Carnegie Mellon
What are the benefits of SASL+Postgresql compared to Postgresql over plain SSL?
SASL is orthogonal to SSL. SASL is an application-layer library
and can be run over either regular sockets or SSL. However there
are SASL hooks to tell it that it's running over a secure channel.
The anticipated
At 01:11 AM 5/20/02 -0600, Bear Giles wrote:
What are the benefits of SASL+Postgresql compared to Postgresql over
plain SSL?
The anticipated benefit of SASL is that it would replace all of the
current authetication code with a set of standard plugins. The
authority problem would be reduced
I can see the benefit of SASL as a standard in public exposed network
services like email servers (SMTP, POP, IMAP), where you can support
different email clients which themselves may or may not support SASL and
may use different SASL libraries.
But for Postgresql - communications is
I've been looking at the authentication and networking code and
would like to float a trial balloon.
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
On Sat, 18 May 2002 11:39:51 -0600 (MDT)
Bear Giles [EMAIL PROTECTED] 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
Bear Giles [EMAIL PROTECTED] writes:
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.
To me, new
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?
We would still need the ability to map user identities - pgusers for
those methods
Bear Giles [EMAIL PROTECTED] writes:
1) add SASL. This is a new standards-track protocol that is often
described as PAM for network authentication.
To me, new standards-track protocol translates as pie in the sky.
When will there be tested, portable, BSD-license libraries that we
10 matches
Mail list logo
