#34654: Post-normalization performed on the Username field leading to the
bypass of
the whitespace stripping
------------------------------+------------------------------------
Reporter: Sim4n6 | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by Natalia Bidart):
There wasn't a concrete fix discussed, though some voices said:
* normalize_username() already applies NFKC normalization and Python
updates the [https://unicode.org/ucd/ Unicode Character Database] in each
release.
* It'd make sense to update the normalization to include these newly
identified empty characters.
* But, likely Django shouldn't duplicate the UCD and it should rely on
Python's.
Personally, I was wondering if we could signal, visually, the being/end of
the username plus, perhaps, showing the username length? This could be a
small but straightforward improvement (of course this only makes sense in
the templates/forms that Django ships), and perhaps it could serve as a
guide to users to apply to their own forms.
--
Ticket URL: <https://code.djangoproject.com/ticket/34654#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070188b9df1cd7-ff5fbc5e-cb56-4d7e-8ed3-18186bc1ded0-000000%40eu-central-1.amazonses.com.
