From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dallas N Antley <dna+pgsql@clas.ufl.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: 7.4.3 and PAM authentication failures
Date: Mon, 16 Aug 2004 19:35:44 -0400
Message-ID: <18655.1092699344@sss.pgh.pa.us> (raw)
In-Reply-To: <200408162049.i7GKnaS26643@clas.ufl.edu>
References: <200408162049.i7GKnaS26643@clas.ufl.edu>
Dallas N Antley <dna+pgsql@clas.ufl.edu> writes:
> I think I know why pam authentication fails with the pam_unix*
> modules, but would appreciate your opinion.
I think you've proven that the particular PAM modules you are testing
with are useless for programs executing as non-root, but that doesn't
mean the entire concept is broken. Look around ... there are lots of
PAM modules (or at least that's the theory).
BTW, what are those "door_info()" and "door_call()" calls shown in the
truss output? Could it be that those are supposed to get the PAM code
into a higher authorization level?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, dna+pgsql@clas.ufl.edu
Subject: Re: 7.4.3 and PAM authentication failures
In-Reply-To: <18655.1092699344@sss.pgh.pa.us>
References: <200408162049.i7GKnaS26643@clas.ufl.edu> <18655.1092699344@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox