Bug 1204374 - Regression: Feature Removal: Installer Prevents the user to proceed with their chosen password.
Summary: Regression: Feature Removal: Installer Prevents the user to proceed with thei...
Keywords:
Status: CLOSED DUPLICATE of bug 1191842
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-21 13:15 UTC by colin
Modified: 2015-03-23 13:21 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-23 13:21:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description colin 2015-03-21 13:15:34 UTC
Description of problem:

Anaconda Graphical Installer used to allow the user to proceed after warning that their entered password was weak.

Version-Release number of selected component (if applicable):

F22 Alpha, Beta TC2, TC3

How reproducible:

always

Steps to Reproduce:
1. Start an Anaconda installation from test image.
2. Enter a root or user password - the onscreen message evaluates the password strength.
3. Installation is prevented from continuing because the feature that users rely on to continue- the 'press twice to accept weak password' does no longer function.
 

Actual results:

Policy is dictated by the software, not the administrator. :-(
This is both a regression over previous behaviour, and Poor Policy Choice.

Expected results:

The Administrator should be able to define Policy- in this case password policy.

Additional info:

This regression is causing increased unnecessary workload.
   
For a large fleet of development and test VMs securely isolated on a LAN the passwords are generated according to a 'rule of thumb' type formula.

This Regression breaks the existing workflow of their installation and administration.

Comment 1 David Shea 2015-03-23 13:21:37 UTC

*** This bug has been marked as a duplicate of bug 1191842 ***


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