From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Subject: | Re: Design Considerations for New Authentication Methods |
Date: | 2006-11-03 01:02:24 |
Message-ID: | 200611021702.25036.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
All,
> For what it's worth, I heartily support this effort. For most cases,
> it probably isn't necessary, but I can think of several applications
> for SASL/GSSAPI where something weaker will simply not do; in the
> absence of the proposed functionality, I simply wouldn't be able to
> use Postgres for those applications.
I'll also add that there are an increasing number of apps and
authentication environments which use SASL or GSSAPI. Supporting these
means that we are no longer locked out of those companies. I know that
the Solaris folks would prefer us to use GSSAPI.
And if there is some reasonably large number of people using a particular
athentication method, we should support it if someone is offering us the
code. Why would we reject a piece of useful functionality based on a
published standard?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-11-03 02:46:16 | Re: Design Considerations for New Authentication Methods |
Previous Message | Simon Riggs | 2006-11-02 23:57:08 | Re: [PATCHES] WAL logging freezing |