Re: Design Considerations for New Authentication Methods

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Subject: Re: Design Considerations for New Authentication Methods
Date: 2006-11-03 04:12:30
Message-ID: 20061103041229.GS24675@kenobi.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > ... Why would we reject a piece of useful functionality based on a
> > published standard?
>
> Well, size and maintainability of the proposed patch are certainly
> factors in any such decision. As a closely related example, I bet
> we'd have rejected the original Kerberos-support patch if we'd known
> then what we know now. It's been a constant source of bugs ever since
> it went in, and with so few users of the feature, it takes a long time
> to find the problems.

Funny, I really wonder why you feel there's few users of it. I use
kerberos auth on quite a few hosts and I've heard of at least a couple
others on this (not all that frequented) list. Kerberos is really
rather popular, made more so through SSPI and GSSAPI...

Thanks

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mark 2006-11-03 04:18:29 Re: Design Considerations for New Authentication Methods
Previous Message Robert Treat 2006-11-03 03:52:56 Re: bug in timestamp and out of range values