| From: | Adam Jackson <ajax-AT-redhat.com> |
| To: | Development discussions related to Fedora <devel-AT-lists.fedoraproject.org> |
| Subject: | Re: FESCO request to revert password confirmation change in F22 |
| Date: | Fri, 06 Mar 2015 11:07:18 -0500 |
| Message-ID: | <1425658038.5825.83.camel@dmt> |
| Cc: | fesco-AT-lists.fedoraproject.org, anaconda-devel-list-AT-redhat.com |
| Archive‑link: | Article |
On Fri, 2015-03-06 at 10:52 -0500, David Cantrell wrote: Speaking only for myself: yeah, I didn't like it either. I voted against it (asking for a revert) in the 28 February meeting because I was hoping the engineering teams actually involved would be willing to work with each other. That appears not to have happened, which I consider deeply disappointing all around. There wasn't _no_ technical discussion. Plenty of people were willing to point out that pwquality being overzealous was making it reject passwords that would otherwise have passed on F21, or would be expected to be "sufficiently strong" according to whatever metric. Plenty of people were willing to point out the ways policy might vary here depending on the deployment scenario. But nobody was willing to make those ideas manifest in, you know, code. So the technical consideration (I felt) we were left with was not "regressing" relative to F21. That is a stunningly weak justification, given that what we're regressing from wasn't especially well-defined and that we change plenty of things in every release, but here we are. Indeed. I'll bring this back to fesco to find someone to head this up. - ajax -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
