add support for the hybrid mode of Argon2 for passphrases #287
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chrisccoulson
force-pushed
the
add-hybrid-argon2-mode
branch
6 times, most recently
from
12e86c4
to
05fd1ba
Compare
We already allow the memory cost to be set to a value that is greater than 4GiB - only capping the maximum here when benchmarking is used. This handles the threads parameter in the same way.
chrisccoulson
force-pushed
the
add-hybrid-argon2-mode
branch
2 times, most recently
from
f88aa4f
to
b48505c
Compare
Passphrase support currently hardcodes the use of argon2i, which is the data-independent version of Argon2. Whilst this has better side-channel resistance than data-dependent versions, it requires more iterations to protect against time-memory tradeoff attacks. Cryptsetup recently switch to argon2id by default for passphrase hashing, which is the hybrid version that provides a good balance between side-channel resistance and time-memory tradeoff. This introduces support for selecting between the 2 versions for passphrase support. There are other versions of Argon2, such as the data-dependent version which sacrifices side-channel resistance for better resistance against time-memory tradeoff attacks, but this isn't supported by the argon2 go package.
chrisccoulson
force-pushed
the
add-hybrid-argon2-mode
branch
from
b48505c
to
d5b6604
Compare
pedronis
approved these changes
Apr 15, 2024
argon2_test.go
Outdated
Comment on lines
292
to
295
| func (s *argon2Suite) TestModeConstants(c *C) { | ||
| c.Check(Argon2i, Equals, Argon2Mode(argon2.ModeI)) | ||
| c.Check(Argon2id, Equals, Argon2Mode(argon2.ModeID)) | ||
| } |
There was a problem hiding this comment.
I see we have this test that enforces the property but still a bit odd overall
I've just updated this to make |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Passphrase support currently hardcodes the use of argon2i, which is
the data-independent version of Argon2. Whilst this has better
side-channel resistance than data-dependent versions, it requires
more iterations to protect against time-memory tradeoff attacks.
Cryptsetup recently switch to argon2id by default for passphrase
hashing, which is the hybrid version that provides a good balance
between side-channel resistance and time-memory tradeoff.
This introduces support for selecting between the 2 versions for
passphrase support.
There are other versions of Argon2, such as the data-dependent version
which sacrifices side-channel resistance for better resistance against
time-memory tradeoff attacks, but this isn't supported by the argon2 go
package.