On Wed, Oct 23, 2013 at 2:11 AM, Adam Harvey <
[email protected]
<
mailto:[email protected]>> wrote:
"Generating an insecure weak hash as no salt was given: please ensure
the salt parameter is specified and uses a strong hash type in order
to generate a cryptographically secure hash"
I guess this would be one of the longest error message, but it does not
matter.
If there isn't better message, I'll commit with this message in a few days.
How about "No salt parameter was specified. You must use a randomly generated salt and a strong hash function to produce a secure hash."
It doesn't emphasise the "strong" and "weak" as much, but I feel it gets the message acrosss well nonetheless.