Bug 1250936 - Standardized Passphrase Policy
Summary: Standardized Passphrase Policy
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Kurik
QA Contact:
Zach Oglesby
URL:
Whiteboard: ChangeAcceptedF23, SystemWideChange
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-06 10:45 UTC by Jan Kurik
Modified: 2016-09-29 11:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-29 11:25:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jan Kurik 2015-08-06 10:45:45 UTC
This is a tracking bug for Change: Standardized Passphrase Policy
For more details, see: https://fedoraproject.org//wiki/Changes/Standardized_passphrase_policy

Currently a number of places ask users to set passphrases/passwords. Some of them enforce some kind of rules for passphrases/passwords, others different rules. This change would create a common base policy for as many of these applications as possible, allowing for local users or products to override this base in cases they need to do so.

Comment 1 Jan Kurik 2015-09-01 14:54:21 UTC
This message is a reminder that Fedora 23 Change Checkpoint: 100% Code Complete Deadline is on 2015-Sep-08 [1].

Expected bug state is ON_QA - Change has to be code complete and is possible to test it in the Beta release.

Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution.  It's important milestone as contingency plan may be put into effect if the Change that miss this deadline.

In case of any questions, don't hesitate to ask Wrangler (jkurik). Thank you.

[1] https://fedoraproject.org/wiki/Releases/23/Schedule

Comment 2 Kevin Fenzi 2015-09-01 14:59:33 UTC
The anaconda changes should be available per https://bugzilla.redhat.com/show_bug.cgi?id=1250746


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