From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from tesla.newpaltz.edu (tesla.newpaltz.edu [137.140.1.102]) by chiba.3jane.net (Postfix) with ESMTP id 917E9200D0D4 for ; Thu, 21 Feb 2002 23:53:09 -0600 (CST) Received: from res57-81.resnet.newpaltz.edu (res57-81.resnet.newpaltz.edu [137.140.57.81]) by tesla.newpaltz.edu (8.9.3/8.9.3) with ESMTP id AAA29986 for ; Fri, 22 Feb 2002 00:50:34 -0500 (EST) From: "Bruce A. Locke" To: gentoo-dev@gentoo.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 22 Feb 2002 00:51:27 -0500 Message-Id: <1014357102.3574.25.camel@kodiak.chronospace.org> Mime-Version: 1.0 Subject: [gentoo-dev] PAM 0.75-r3: Failure Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: deb6c69a-9483-40c5-ae93-bb81780f0243 X-Archives-Hash: 3236f101b556d840f22c6e7e988efbac Hello... After spending almost three solid nights working on it I've given up trying to upgrade so we can have pam_stack and pam_console. After spending hours trying to track down the source of an error, changing pam.d files a zillion times, recompiling pam and shadow a zillion times, etc, I'm giving up for now. I keep getting the same retarded undescriptive error message over and over (PAM_ABORT) which is _only_ used in 83+ different parts of the pam source code I'm getting nowhere. Whoever coded Pam obviously was alergic to logging real error messages and just have every damn test return error codes. As far as I can tell the problem only affected the shadow package (passwd, chfn, etc). But thats a serious enough problem on its own. Some interesting facts: The latest official release is Pam 0.75 - Redhat 7.2 ships Pam 0.75 with over 50 patches, not including pam_stack and friends which are not in Pam 0.75 - Redhat ships with a copy of shadow-utils thats a month or two older then our current unmasked one - Shadow-4 will not build against Pam 0.75 + Redhat patches - Mandrake ships pam as a big tarball with many of the Redhat patches and most likely a few of its own - Mandrake ships with a passwd command that _isn't_ part of the shadow package ( no, it didn't work either :( ) - Debian is stuck at Pam 0.73...? What does it mean? Hell if I know :( Sorry folks... if anyone wants to take a crack at it feel free... I'd recommend starting with the mandrake tarball. Its alot easier then dealing with 50+ patches. -- Bruce A. Locke blocke@shivan.org