Red Hat Bugzilla – Bug 225860
python binding behaves poorly when specifying dictpath
Last modified: 2007-11-30 17:07:28 EST
+++ This bug was initially created as a clone of Bug #224347 +++
FascistCheck() exhibits two problems when specifying a dictpath:
1.) It checks for the existence of the path, not the path plus ".pwd" as with
the default. This means you can't specify an alternative path at all because
it'll throw an exception in any case. You can't work around it either because
2.) if you specify the path plus ".pwd" yourself, the python module now finds
the file, passes path+".pwd" to cracklib which barfs on the non-existence of
path+".pwd.pwd" and apparently calls exit() or something else which ends the
python interpreter (without traceback or other such superfluopus things ;-).
Version-Release number of selected component (if applicable):
Judging from the code, this problem exists in Rawhide (cracklib-2.8.9-6) as well.
Steps to Reproduce:
1. Run this test program:
--- 8< ---
from cracklib import *
for path in ('/usr/share/cracklib/pw_dict', '/usr/share/cracklib/pw_dict.pwd'):
print FascistCheck ('foo', path)
except Exception, e:
[Errno 2] No such file or directory: '/usr/share/cracklib/pw_dict'
/usr/share/cracklib/pw_dict.pwd.pwd: No such file or directory
PWOpen: Illegal seek
No traceback with the first path in the list, a (caught) traceback with the
second path, and the line "foo".
-- Additional comment from email@example.com on 2007-01-25 12:33 EST --
Quite right. Fixing in Raw Hide shortly. Let me know if you need this updated
in FC6 as well.
-- Additional comment from firstname.lastname@example.org on 2007-01-29 11:48 EST --
As I have dicovered now, I don't need to specify the dictpath to use the
standard dictionary. Would it be much work to change the module so that "pydoc
cracklib" on the cmdline or "help(FascistCheck)" from within python would
mention that, i.e. not only have "FascistCheck(...)" without the arguments?
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.