Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unicode collision: stringprep, saslprep #7

Open
westurner opened this issue Jul 11, 2013 · 1 comment
Open

Unicode collision: stringprep, saslprep #7

westurner opened this issue Jul 11, 2013 · 1 comment

Comments

@westurner
Copy link

The stringprep routines in passlib.utils.saslprep may be relevant to some of the usecases for unicode-slugify.

References

@nitely
Copy link
Contributor

nitely commented Jan 3, 2018

Everything described by rfc4013 (Stringprep) seems to be covered by slugify. It does NFKC (normalization form into compatibility decomposition + canonical composition), then keeps characters defined as letter or number by the unicode character database (so, no invisible characters).

That said, why anyone would use unicode for usernames is beyond me. There are plenty of chars that look alike.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants