Created attachment 745066 [details] selecting gb keyboard and lang Description of problem: Bug 646876 describes the case from F13/F14 where non-ascii character were not allowed in passwords at install, but could be added by the passwd command later. Version-Release number of selected component (if applicable): How reproducible: 100 % Steps to Reproduce: 1. select the GB keyboard 2. enter shift-3 as a characer in the password 3. Actual results: cannot use british pound symbol in password Expected results: Should be able to use symbol Additional info:
Created attachment 745067 [details] denies as a root password
Created attachment 745068 [details] denied as a user password
Created attachment 745072 [details] passwd command allows for non-ascii character
Both Alpha and Beta release criteria call for "The installer must run" as a criterion. I would propose it can be argued that if a password accepted by the installed system is rejected by the installer then the installer is broken. and broke equates to not running.
Discussed at 2013-05-08 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-08/f19beta-blocker-review-4.2013-05-08-16.00.log.txt . Nice attempt at criteria gymnastics Bob, a solid C+, but no, you can't arbitrarily redefine any bug in anaconda as 'broken' and 'broken' as 'not running' :) This clearly doesn't infringe any of the criteria and has a very obvious 'workaround' (don't put whatever characters anaconda is barfing on in your password). It was rejected as a blocker.
Anaconda will now allow, but warn about, non-ASCII characters in a password.