DJ Lucas wrote these words on 07/17/05 16:19 CST: > Haven't created anything yet except the shadow patch, but I did go ahead > and get notes ready for upgrade of all three (cracklib-pam-shadow), but > didn't want to proceed untill I had a test case availble so that Heimdal > didn't get broken.
I took a look at the new Cracklib and it looks simple enough to create a new patch to create a libcrack_heimdal library and associated header file. I want to rename the lib from libcrack_krb5 to libcrack_heimdal as MIT Kerberos is not set up to use Cracklib. Here are some other notes: 1. It appears to check for X, specifically libICE (the configure script has notes this is required for SunOS). I'm not sure what would happen if it doesn't find the X lib. I didn't follow the configure script to find out (damn auto-tools long-ass scripts). We need to determine whether or not to list X as a dependency. 2. It creates a static library now (no big deal). 3. There is a test program using the test-data I believe first originated on this list! Anyway, here's the million dollar question: If I can get patches for Cracklib and Heimdal prepared tonight or tomorrow, are we going to try to get the new Cracklib into BLFS before the release of 6.1? If so, we need to thoroughly check out /cracklib/pam/shadow. I suppose we would want to update the book to the latest PAM as well. I can check out and confirm proper working with Heimdal. DJ sent me a patch to update Shadow to 4.0.9, so this will go in tonight. Do we have enough time before release to thoroughly test out the Cracklib/PAM/Shadow combination before release? If the answer to this question is no, then I'll probably postpone working on the Cracklib patches until after release. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 18:44:00 up 111 days, 18:17, 2 users, load average: 0.00, 0.00, 0.00 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
