Skip to content
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

must-update? should also accept explicit parameters #30

Open
coreagile opened this issue Apr 22, 2024 · 0 comments
Open

must-update? should also accept explicit parameters #30

coreagile opened this issue Apr 22, 2024 · 0 comments

Comments

@coreagile
Copy link

For my uses, the default parameters for :argon2id aren't sufficient for my hardware, so I hash with an extra iteration. Sadly, when I verify a password, it always comes back with {:update true} because passwords are always hashed with custom parameters.

I should be able to pass those explicit parameters to verify, so it can then pass those along to must-update?

For example:

(hashers/verify attempt encrypted {:limit #{:argon2id}, :params {:iterations 3, :memory 65536, :parallelism 1}})

Alternatively, we should be able to reset the global parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant