For ex, adding the Django Code Snippet for handling User names in the Login
Page :
default_username = (unicodedata.normalize('NFKD', default_username)
So Django does follow Normalizing of Usernames usign NFKD Algorithm.
Then applies Hashing Algorithms on this.
*But the same is never followed for Passwords.*
Is this done on Purpose that the HASHING algorithm takes care of whatever
required and Normalization isnt quite required for such purpose.
Even the Django Documentation does'nt talk about Unicode Normalizing on
Passwords but you can still find it for Other forms of Text inputs.
On Wednesday, April 20, 2016 at 7:52:27 PM UTC+5:30, Rick Leir wrote:
>
> There is also a new issue in Trac on this topic. I added two links to
> Stackoverflow discussions there.
>
> The issue: supposing a password is mañana. Depending on what client you
> use, input methods can give you two different UTF8 characters for ñ. As a
> first step, let's add test case, and check whether it fails.
>
> My guess (tho I am new to this) is that this is a Django issue not Python.
> Cheers-- Rick
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/90031b13-bac4-4601-a684-fd10dcab27a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
