-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please provide byte array based hashing #99
Comments
Hi @scubajorgen, this is a good feature to implement. |
I used password4j Argon2d in my project to decrypt KeePass databases. Did conversion from raw byte[] to String for the seed and password (using various charactersets). However I could not get this working. I suspected the byte[]->String->byte[] conversion based on your source code. Therefore I did a comparison of the result of password4j and BouncyCastle/Spring and they differed. I made a quick and dirty copy of your password4j argon function (I hope I did not violate licences) and removed the String stuff. It worked. You can use my unit test, testHashTimed() as a working example. |
Hi @scubajorgen , @JorgenVanDerVelde version 1.7.0 is now public with public APIs accepting See the changelog for further information. |
Thanx! I tested your software in my code to decrypt Keepass databases and it worked out fine!! Thanks for your great work. |
Thanks for this great project
A problem is that it is not possible to use the hashing based on raw byte arrays.
I tried to use Argon2 hashing with a raw byte array as salt and a password consisting of raw bytes.
(This is the way argon2d and argon2id are used to decrypt Keepass databases)
However it is impossible to insert these arrays. It can only be done by creating a String out of the bytes and then pass the strings. However, under the hood the Strings/CharSequences are converted to bytes again. However some UTF8 decoding takes place, not resulting in the original byte arrays!
It would be great to have a version also including hash functions that take byte arrays as input
The text was updated successfully, but these errors were encountered: