Re: [Fwd: PAM Critical error, but no logging]
Okay, (Doh!) it looks like I don't have the cracklib_dict.pwd file
installed on the system where PAM doesn't work with cracklib. I've
tried apt-get remove-ing and re-installing any crack-related packages
I've been able to find using apt-cache, but still no *_dict.* files.
I've also searched the old mailing list archives for this, so either
this is a bug or anomaly in the progression of packages, and in either
case there's no evidence anybody has known about it up until now. I'm
betting it's a part of some normal package I'd put in on a complete
install but which I just cannot presently think of. At any rate, I'd
like two forms of feedback:
1) What is the stable package I need to install to get these *_dict.*
files?
2) Does anyone have any suggestions on how to better search for this
kind of problem using the apt-* facilities?
TIA. I'll forward the final results to the pam-list, as I presume most
of you are not on that. See Igmar's comments below for more
information.
Sincerely, Xeno
> Igmar Palsenberg wrote:
>
> Hi,
>
> This is the actual problem :
>
> stat("/var/cache/cracklib/cracklib_dict.pwd", 0xbfff9a1c) = -1 ENOENT
>
> It's also consitent with the code (pam_cracklib.c) :
>
> if (!stat(buf,&st) && st.st_size)
> return PAM_SUCCESS;
> else {
> if (ctrl & PAM_DEBUG_ARG)
> _pam_log(LOG_NOTICE,"dict path '%s'[.pwd] is invalid",
> CRACKLIB_DICTPATH);
> return PAM_ABORT;
> }
>
> In other words : It can't find your dicts file. What I do find strange it
> the path it is looking for : /var/cache/cracklib. On all RH systems I've
> been on it's in /usr/lib
>
> You have two options : Make a symlink, copy the files, etc, or recompile
> the cracklib module.
>
> Igmar
--
http://www.eskimo.com/~xeno
xeno@eskimo.com
Physically I'm at: 5101 N. 45th St., Tacoma, WA, 98407-3717, U.S.A.
Reply to: