-
Notifications
You must be signed in to change notification settings - Fork 139
convenience Functions for KDFs #147
Comments
This would certainly make sense for argon2, since it has a standard format for the encoded hash and parameters. The BCrypt code already has high-level functions. For scrypt it's a bit trickier, as there's no standard format that I'm aware of for encoding the hash. The Haskell |
I wasn't aware that the PHC specified a format for hash storage. I agree that that should be used. No need to define something new :-) So i think we should add some |
I'm not sure about |
Agreed. I think I'll just implement this as soon as i find the time and send a pull request when I'm done. Probably much more productive to talk about actual code at this point. |
Note that the format described in that repo is wrong. There's also a 'v' parameter in the string which is the argon2 version. Also rather confusingly, the version is entered as a base-16 parameter for the |
@tauli Did you make any progress on this? I looked into the argon2 side, it looks like https://github.com/P-H-C/phc-winner-argon2 recommends using |
@MaxGabriel I wrote some code to do this which you can use in the meantime if you wish. I will move it to cryptonite at some point when I've tidied it up and added some docs. |
I'd like to see some convenience functions for the KDFs akin to the
encryptPass
andverifyPass
from the packagescrypt
.If this is something that you would like to see but don't have the time to implement yourself, i'd be happy to contribute a pull request.
The text was updated successfully, but these errors were encountered: