You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now when a user submits a hashfile where the username contains a non utf-8 character (åøß e.g.) hashview cannot parse it correctly. Two potential fixes:
hex/base64 encode user names:
Pro: allows for quick solution
Con: Harder to do case insensitive searches.
Convert database language support to handle non utf-8 characters
pro: allows for case insensitive searchs
con: might require table migrations for existing hashfiles
if we go with second solution we should probably convert the hashes table too while we're at it.
The text was updated successfully, but these errors were encountered:
Right now when a user submits a hashfile where the username contains a non utf-8 character (åøß e.g.) hashview cannot parse it correctly. Two potential fixes:
hex/base64 encode user names:
Pro: allows for quick solution
Con: Harder to do case insensitive searches.
Convert database language support to handle non utf-8 characters
pro: allows for case insensitive searchs
con: might require table migrations for existing hashfiles
if we go with second solution we should probably convert the hashes table too while we're at it.
The text was updated successfully, but these errors were encountered: