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
Is your feature request related to a problem? Please describe.
My database has passwords that are salted and hashed with BCrypt. Currently I'm using the random characters anonymization, but when developers look at the anonymized database, they think we're using a different hashing mechanism because they see hexadecimal.
Describe the solution you'd like
If a BCRYPT anonymizer existed, it could output strings like: $2<a/b/x/y>$[cost]$[22 base64 characters][31 base64 characters]
Describe alternatives you've considered
I could configure the characters in the current anonymizers to use the full base64 set, but that still wouldn't look like a BCrypt hash to the developers.
Additional context
I'd be happy to PR this back in if there's interest!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
My database has passwords that are salted and hashed with BCrypt. Currently I'm using the random characters anonymization, but when developers look at the anonymized database, they think we're using a different hashing mechanism because they see hexadecimal.
Describe the solution you'd like
If a
BCRYPT
anonymizer existed, it could output strings like:$2<a/b/x/y>$[cost]$[22 base64 characters][31 base64 characters]
Describe alternatives you've considered
I could configure the characters in the current anonymizers to use the full base64 set, but that still wouldn't look like a BCrypt hash to the developers.
Additional context
I'd be happy to PR this back in if there's interest!
The text was updated successfully, but these errors were encountered: