Red Hat Bugzilla – Bug 983449
No “weak password" indication when set a weak password
Last modified: 2014-01-21 14:45:36 EST
Created attachment 772095 [details] strong password Description of problem: No “weak password" indication when set a weak password(e.g. redhat). Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20130222.0.auto1716.el6 ovirt-node-3.0.0-1.999.20130701111251git99aadc6.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Boot from PXE and install RHEV-H 6.5. 2. Enter setup password page and input a weak password(e.g.redhat). 3. Actual results: No “weak password" indication when set a weak password(e.g. redhat). Expected results: There should a tip to inform the user like 6.4. "You have provide a weak password! Storage passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words" Additional info:
Fixed in http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=commit;h=92042c92ee173f35dd36dbfd2a3206560b678571 But maybe this should be reworked, see also bug 986281
rhev-hypervisor6-6.5-20131017.0 ovirt-node-3.0.1-4.el6.noarch 1. Boot from PXE and install RHEV-H 6.5. 2. Enter setup password page and input a weak password(e.g.redhat). Hit will show: "You have provide a weak password! Storage passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words. Reason: it is WAY too short" So the bug is fixed, change bug status to VERIFIED.
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0033.html