Re: Patch to include PAM support...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Dominic J(dot) Eidson" <sauron(at)the-infinite(dot)org>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch to include PAM support...
Date: 2001-06-13 14:08:37
Message-ID: 200106131408.f5DE8br04024@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> The interaction that a PAM stack can initiate is limited to prompting for
> one or more values and getting strings as an answer. The PAM-using
> application registers a "conversation function" callback, which is
> responsible for issuing the prompt and getting at the data in an
> application-specific manner. Ideally, the libpq protocol and API would be
> extended to support this generality, but based on Dominic's comments the
> password exchange would work to support the useful subset of this
> functionality without any protocol or API changes.
>
> Most of the time, PAM is used as a wrapper around some password database
> like NIS or LDAP (or maybe even PostgreSQL).

We now have enough "yes" votes to apply this patch. I will give another
day for comments on the patch's contents.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jean-Michel POURE 2001-06-13 14:37:16 SELECT Field1 || Field2 FROM Table
Previous Message Bruce Momjian 2001-06-13 14:07:37 Re: Indexing on a separate volume

Browse pgsql-patches by date

  From Date Subject
Next Message Marko Kreen 2001-06-13 14:36:06 Re: reset all update
Previous Message Bruce Momjian 2001-06-13 13:48:15 Re: 7.1 odbc bug & patch