As far as I can tell every password hashing function that uses the crypt(3) interface uses a little endian encoding as implemented in Base64ShaCrypt, including legacy descrypt.
In other words Base64Crypt was a mistake and isn't useful as a non-standard big endian variant of the crypt(3) encoding.
Should we deprecate it, and possibly try to give Base64ShaCrypt a better name, as it's the Base64 encoding used for every crypt(3)-compatible MCF hash?
As far as I can tell every password hashing function that uses the
crypt(3)interface uses a little endian encoding as implemented inBase64ShaCrypt, including legacydescrypt.In other words
Base64Cryptwas a mistake and isn't useful as a non-standard big endian variant of thecrypt(3)encoding.Should we deprecate it, and possibly try to give
Base64ShaCrypta better name, as it's the Base64 encoding used for everycrypt(3)-compatible MCF hash?