Bug 1230293
| Summary: | anaconda 23.9-1 has reverted to requiring a complex password | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | satellitgo |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, kvolny, lsatenstein, robatino, satellitgo, scottro11, vanmeeuwen+fedora |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-11 12:35:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
satellitgo
2015-06-10 14:55:05 UTC
Anaconda added a means of configuring the password policy through the pwpolicy kickstart command, so it is up to the spins to define a password policy. This was discussed in https://fedorahosted.org/fesco/ticket/1412, and the only reason the change was reverted for F22 was because FESCO decided there was not enough time to create a distro- (or products-) wide password policy. however this does not address the boot.iso (netinstall) password usecase which this bug discusses. *** Bug 1246771 has been marked as a duplicate of this bug. *** I believe comment #2 is a valid concern also, I don't believe something like "write your own kickstart which would let you go without password at all" is a good answer when I just want to do something like 'qemu-kvm -cdrom some-install.iso fedora-scratch.qcow2' and click through, not having to spend half a day studying what is this kickstart thing all about ... (In reply to Karel Volný from comment #4) > I believe comment #2 is a valid concern Please think via the ongoing discussion that was set up for exactly this purpose instead of harassing people via bug statuses. *** This bug has been marked as a duplicate of bug 1250746 *** The password rules in Annaconda should match the default rules from Fedora Linux. Fedora Linux allows me to enter #xxxxx001 (for example), but anaconda rejects that password. xxxxx or xxxxxx , when pre-pended with # and post pended by 001, or 002, are accepted by Fedora Linux, but not by annaconda. To complete my installation I use password #montreal001 for root and user. After booting, I change the root and user passwords to comply with Linux rules. Please reopen bug against anaconda password rule adherence. At least allow done/done to force acceptance of presented password. The password rules in Annaconda should match the default rules from Fedora Linux. Fedora Linux allows me to enter #xxxxx001 (for example), but anaconda rejects that password. xxxxx or xxxxxx , even when pre-pended with # and post pended by 001, or 002. The format #xxxxxx00n is accepted by Fedora Linux, but not by annaconda. xxxxxx = eilsel or eirual or guest To complete my installation with Fedora 23 I use password #montreal001 for root and user, so as to avoid problems. After booting, I change the root and user passwords to comply with and respecting the Linux rules. Please reopen bug against anaconda password rule adherence. At least allow done/done to force acceptance of presented password. |