Skip to content

Adding RFC 9106 cost profiles? #8

@fnordfish

Description

@fnordfish

RFC 9106 describes different default profiles depending on available memory:

If a uniformly safe option that is not tailored to your application or hardware is acceptable, select Argon2id with t=1 iteration, p=4 lanes, m=2^(21) (2 GiB of RAM), 128-bit salt, and 256-bit tag size. This is the FIRST RECOMMENDED option.

If much less memory is available, a uniformly safe option is Argon2id with t=3 iterations, p=4 lanes, m=2^(16) (64 MiB of RAM), 128-bit salt, and 256-bit tag size. This is the SECOND RECOMMENDED option.

Apart from the memory cost factors, they differ from the OWASP recommendation using p=4 lanes.

Also, for testing, it might be useful to have a pre-configured cheapest option with t=1, m=2^3, p=1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions