-
Notifications
You must be signed in to change notification settings - Fork 30
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
aead/argon2 archived, moved to x/crypto/argon2 #36
Comments
Keepass2 uses Argon2d. https://github.com/aead/argon2 exposes usage of Argon2d. The official x/crypto/argon2 package does not. There are even issues around that, with discussions about this very matter, which have been shut down with the argument, that they do not want to expose unsafe options that shouldn't be used, even though argon2d is fine for an offline version as used in keepass2. It is therefore not possible to move th x/crypto/argon2 without getting that functionality exposed. https://github.com/golang/crypto/blob/master/argon2/argon2.go#L102 is not exposed https://github.com/golang/crypto/blob/master/argon2/argon2.go#L74 uses argon2i https://github.com/golang/crypto/blob/master/argon2/argon2.go#L98 uses argon2id |
Here is the issue golang/go#23602 where this is mentioned.
As this is only an implementation working on compatibility with standard Keepass2, and Keepass2 uses argon2d, the "if possible" part is not fulfilled |
Closed for lack of activity. |
From https://github.com/aead/argon2:
The text was updated successfully, but these errors were encountered: