Skip to content

must-update? should also accept explicit parameters #30

Open
@coreagile

Description

@coreagile

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions