Re: Issue with Django Password Normalization

Here are links to the dev discussions. https://groups.google.com/d/msg/django-developers/MBSWXcQBP3k/XgWzGhpDBAAJ On Thursday, 21 April 2016 10:47:43 UTC-4, Arun S wrote: > > thanks for some very useful information. > > I did raise this in the dev forum but it was not agreed to be a question > in

Re: Issue with Django Password Normalization

username = models.CharField( _('username'), max_length=150, unique=True, help_text=_('Required. 150 characters or fewer. Letters, digits and @/./+/-/_ only.'), validators=[ validators.RegexValidator( r'^[\w.@+-]+$', It looks as if you could just clear the LOCALE

Re: Issue with Django Password Normalization

normalize the chars. And as you say, it is a topic for the dev list. But how important is this issue? Yes, it is security related. But it is far from critical in my mind. On Wednesday, 20 April 2016 10:22:27 UTC-4, Rick Leir wrote: > > There is also a new issue in Trac on this topic. I ad

Re: Issue with Django Password Normalization

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 wh