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
{{ message }}
This repository has been archived by the owner on Oct 19, 2018. It is now read-only.
One way to avoid this is by pre-hashing passwords with something like sha256 or sha512. This should always give us a fixed byte length. However, this leads to the issue that the sha hash effectively becomes the password, meaning one would lose the maximum possible entropy when using high-entropy passwords. On the other hand, it may actually increase the entropy of most common passwords, as long as they're not part of rainbowtables.
I'm not quite sure how to go about this, so any feedback would be appreciated.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The issue is that technically, bcrypt can only handle 72 bytes of data, minus one byte for the null terminator.
One way to avoid this is by pre-hashing passwords with something like sha256 or sha512. This should always give us a fixed byte length. However, this leads to the issue that the sha hash effectively becomes the password, meaning one would lose the maximum possible entropy when using high-entropy passwords. On the other hand, it may actually increase the entropy of most common passwords, as long as they're not part of rainbowtables.
I'm not quite sure how to go about this, so any feedback would be appreciated.
The text was updated successfully, but these errors were encountered: