A lightbulb popped up over my head after reading this piece:
http://www.squid-cache.org/mail-archive/squid-users/200112/0960.html
So instead of ./pam_auth, I tried ./digest_pw_auth. The resulting error gave the clue:
Usage: digest_pw_auth [OPTIONS] <passwordfile>
-c accept digest hashed passwords rather than plaintext in passwordfile
BTW, why is it that I have to do the full "make" in /path/to/squid-3.0-PRE3 and wait for it to error out, before I can get a successful "make" in ./helpers? If I skip straight to "make" in ./helpers, it invariably fails with "ld: can't locate file for: -lmiscutil".
>My understanding after searching squid-users and squid-dev is that in order to use Apache-style digest password file with Squid 2.5STABLE5, one needs the digest_pw_auth from Squid 3.0DEV. Is this correct?
>
>Since squid-3.0-PRE3-20040605 still errors out on Mac OS X with "MemBuf.cc:285:" during a full "make", I did a "make" only from within ./helpers. Then I went inside ./helpers/digest_auth/password and did "sudo make install" from there. I verified "/usr/local/squid/libexec/digest_pw_auth" was replaced by the new copy. However, after restarting, my Squid 2.5STABLE5-20040605 still does not understand scrambled digest password file generated by Apache 1.3.29. To be sure, I pasted the encrypted digest password string directly into the auth popup. That unfortunately worked, which means Squid 2.5STABLE5 is still behaving as if it's operating with the original digest_pw_auth.
>
>Anyone has a hint?
>
>Reference:
>http://marc.theaimsgroup.com/?l=squid-dev&m=108629361406031&w=2
Received on Tue Jun 08 2004 - 21:37:49 MDT
This archive was generated by hypermail pre-2.1.9 : Thu Jul 01 2004 - 12:00:02 MDT