Null characters in return buffer

[paixaop]

Null characters in return buffer

[richchurcher]

Isn't it by design? In the libsodium docs it says,

The generated key has the size defined by the application, no matter what the password length is.

Assuming that the output buffer is always the same size but is null-padded, it would follow that to store the key in a database as a string, you'd need the string to be padded too. Otherwise when you regenerate the key in crypto_pwhash_argon2i_str_verify you'd not end up with the same result.

[jedisct1]

crypto_pwhash_argon2i_STRBYTES represents the maximum length of the returned string.

The string itself can be shorter, and should be trimmed after the first \0, even though the verification function will tolerate padding after it.

[richchurcher]

I see! Thanks, that's helpful.

[rflaperuta]

Do I need to close the Issue Before or After the PR is merged?

Thanks for the help.

[sarahscheffler]

Is it documented somewhere that you have to strip off the \0 bytes? Or is there any interest in removing them automatically? We just had the same issue encoding/decoding from base64 and it took us a little while to track down the error.