Bug 170742 - Revelation password check fails to check dictionary words
Revelation password check fails to check dictionary words
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: revelation (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Thorsten Leemhuis
Fedora Extras Quality Assurance
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-10-14 07:48 EDT by Tim Waugh
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-14 12:45:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
revelation-spec-diff (684 bytes, patch)
2005-10-14 07:53 EDT, Tim Waugh
no flags Details | Diff

  None (edit)
Description Tim Waugh 2005-10-14 07:48:35 EDT
Description of problem:
Revelation password check has a bug that causes very insecure passwords to be
classed as "strong".

Version-Release number of selected component (if applicable):
0.4.5-2.fc4

How reproducible:
100%

Steps to Reproduce:
1. View->Password Checker
2. Type in: mypassword
  
Actual results:
"The password is good"

Expected results:
"The password is based on a word"

This is happening because crack.so is looking in the wrong place for its
dictionary.  Patch to follow.
Comment 1 Tim Waugh 2005-10-14 07:53:44 EDT
Created attachment 119970 [details]
revelation-spec-diff

Here's the fix.
Comment 2 Thorsten Leemhuis 2005-10-14 12:45:29 EDT
(In reply to comment #0)
> Description of problem:
> Revelation password check has a bug that causes very insecure passwords to be
> classed as "strong".

Fixed in cvs and new packages build. But I used a different fix -- it uses the
cracklib-dicts package from core now (as it should have done from the beginning)
and not the dict that is shipped with revolution (that is removed during
%install now).

Note You need to log in before you can comment on or make changes to this bug.