Timeline for Argon2i versus Argon2d?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2018 at 1:46 | history | tweeted | twitter.com/StackCrypto/status/957067298573115392 | ||
| Dec 14, 2017 at 15:36 | comment | added | Frank Denis | Use Argon2id, which combines Argon2i and Argon2d, and is what the Argon2 authors now recommend. | |
| Dec 14, 2017 at 10:34 | history | edited | e-sushi | CC BY-SA 3.0 |
edited title
|
| Jul 9, 2017 at 23:32 | comment | added | user40185 | I agree with SEJPM; use Argon2d. You see Argon2i recommended a lot because Argon2 is also used for server side password-based authentication, but this is quite a different use case from local key derivation. Plus, on mobile devices where people pick bad passwords and you can't jack up the difficulty parameters as much, you'll want Argon2d's better tradeoff resistance. | |
| Jun 10, 2017 at 12:47 | vote | accept | Shahid Thaika | ||
| Jun 10, 2017 at 12:44 | answer | added | SEJPM | timeline score: 11 | |
| Jun 8, 2017 at 19:42 | comment | added | SEJPM | Argon2 has seen a lot of scrutiny and is a good choice thus. As you have a client-side-only application where you probably have bigger problems if the attacker can pull cache-timing or related side channel attacks off, you are fine with Argon2d (KeePass also uses Argon2d). Side-channel resistence (like with Argon2i) is "critical" when you have a scenario like a public cloud service provider with shared hosts. | |
| Jun 8, 2017 at 1:36 | history | asked | Shahid Thaika | CC BY-SA 3.0 |