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
The salt SHALL be at least 32 bits in length and be chosen arbitrarily so as to minimize salt value collisions among stored hashes. Both the salt value and the resulting hash SHALL be stored for each subscriber using a memorized secret authenticator.
This may be a nitpick, but using the word arbitrarily is dissatisfactory. It is not a technical term and it is not defined in the standard. Looking up the word in Merriam Webster:
based on or determined by individual preference or convenience rather than by necessity or the intrinsic nature of something.
existing or coming about seemingly at random or by chance or as a capricious and unreasonable act of will.
(and other definitions that don't help in this context)
It is incongruous to read a sentence about cryptography that indirectly refers to "individual preference", "convenience", "by chance", "capricious" and "seemingly at random".
The text was updated successfully, but these errors were encountered:
In SP800-63b 5.1.1.2 Memorized Secret Verifiers:
This may be a nitpick, but using the word arbitrarily is dissatisfactory. It is not a technical term and it is not defined in the standard. Looking up the word in Merriam Webster:
(and other definitions that don't help in this context)
It is incongruous to read a sentence about cryptography that indirectly refers to "individual preference", "convenience", "by chance", "capricious" and "seemingly at random".
The text was updated successfully, but these errors were encountered: