base64 encoding of username in the user table does not add any security, but it adds complexity to the code and is annoying when debugging the database
Using "crypt" to name a function UserIdentifier::login64crypt() that only encodes a string in base64 is incorrect and misleading.
Let's get rid of this and then concentrate on adding complexity where it will be useful: using standard cryptographic password hashing methods.
base64 encoding of username in the user table does not add any security, but it adds complexity to the code and is annoying when debugging the database Using "crypt" to name a function UserIdentifier::login64crypt() that only encodes a string in base64 is incorrect and misleading. Let's get rid of this and then concentrate on adding complexity where it will be useful: using standard cryptographic password hashing methods.