Évite une erreur 500 dans la validation du pseudo s'il contient \x00 #6511
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug rapporté par Sentry : un plaisantin a essayé de s'inscrire avec un pseudo contenant le caractère 0x00 (notation octale, en Python c'est
\x00). Ce caractère est mal géré (yamatt/homoglyphs#6) par la bibliothèque qu'on utilise pour s'assurer que le pseudo ne ressemble pas visuellement à un pseudo déjà existant, et lève uneValueErrorqui n'était pas rattrapée.Le correctif est un peu moche, mais il fonctionne...
Contrôle qualité
Puisque le caractère fautif est un peu compliqué à manipuler, je dirais que la CI devrait être suffisante, puisque j'ai ajouté un test. Si vraiment vous voulez tenter des choses, l'encodage du caractère dans la requête POST (si vous êtes motivé pour faire du curl), c'est
%00.