X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 419955E46C5 for ; Mon, 16 Aug 2004 23:06:49 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 46770-02 for ; Tue, 17 Aug 2004 02:06:49 +0000 (GMT) Received: from clas.ufl.edu (minotaur.clas.ufl.edu [128.227.148.248]) by svr1.postgresql.org (Postfix) with ESMTP id 867D85E46BF for ; Mon, 16 Aug 2004 23:06:46 -0300 (ADT) X-Envelope-From: dna@clas.ufl.edu Received: from clas.ufl.edu (mail.clas.ufl.edu [128.227.148.252]) by clas.ufl.edu (8.11.7p1+Sun/8.11.7/clas1.20) with ESMTP id i7H26nS27612; Mon, 16 Aug 2004 22:06:49 -0400 (EDT) Message-Id: <200408170206.i7H26nS27612@clas.ufl.edu> From: Dallas N Antley To: Tom Lane Subject: Re: 7.4.3 and PAM authentication failures In-reply-to: Your message of "Mon, 16 Aug 2004 19:35:44 EDT." <18655.1092699344@sss.pgh.pa.us> Cc: pgsql-admin@postgresql.org Date: Mon, 16 Aug 2004 22:06:49 -0400 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/138 X-Sequence-Number: 14533 /- On Monday (8/16/2004 19:35) Tom Lane wrote: > Dallas N Antley 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). Correct. I'm only referring to pam_unix* modules. This has come up on the list a few times, but there's never been a "solution" in any of the replies. http://archives.postgresql.org/pgsql-admin/2003-02/msg00301.php http://archives.postgresql.org/pgsql-admin/2003-01/msg00352.php http://archives.postgresql.org/pgsql-admin/2002-10/msg00066.php http://archives.postgresql.org/pgsql-admin/2002-08/msg00281.php http://archives.postgresql.org/pgsql-admin/2002-06/msg00110.php http://archives.postgresql.org/pgsql-admin/2002-05/msg00233.php http://archives.postgresql.org/pgsql-admin/2002-05/msg00075.php This is why login, dtsession, xscreensaver, etc are setuid under Solaris, and probably under Linux distributions that use /etc/shadow, C2-NIS, and/or NIS+. Given the current security model employed by the postmaster process, this wouldn't be trivial. Considering the number of times this came up in the archives, and after getting stuck myself, I'd like to get this added to the FAQ, assuming I'm correct in my logic. > 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? Doors are a Solaris-specific (AFAIK) type of inter-process communication -- similar to sockets, but faster. They're used inside the PAM libraries for name service, syslog calls, etc. Dallas