Timeline for Why does Argon2 truncate BLAKE2b outputs?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2024 at 11:54 | vote | accept | samuel-lucas6 | ||
| May 19, 2024 at 11:54 | answer | added | samuel-lucas6 | timeline score: 3 | |
| Jan 22, 2024 at 16:34 | comment | added | samuel-lucas6 | @MaartenBodewes I haven't but seeing as nobody has answered, I'll do that. I've had mixed success emailing academics/engineers so it's not my go-to approach. | |
| Jan 21, 2024 at 22:30 | comment | added | Maarten Bodewes♦ | A by now classic remark for "why" questions: have you tried to contact the authors? If possible it would be great if they or otherwise you could post the answer here. | |
| Jan 21, 2024 at 16:48 | comment | added | samuel-lucas6 | @kelalaka Yes, I'm aware of that, but truncation results in more computation (more hashing) for larger outputs. Deriving a short output hasn't been slowed down. It doesn't seem like domain separation when V1 is the same as a digestSize = 64. | |
| Jan 21, 2024 at 16:07 | comment | added | kelalaka | Because it is designed for password hashing where there is no collision problem so 256-bit is enough for all. | |
| Jan 21, 2024 at 10:46 | history | asked | samuel-lucas6 | CC BY-SA 4.0 |