crypt: make scrypt memory parameter configurable#9170
Open
fuldeka wants to merge 1 commit intorclone:masterfrom
Open
crypt: make scrypt memory parameter configurable#9170fuldeka wants to merge 1 commit intorclone:masterfrom
fuldeka wants to merge 1 commit intorclone:masterfrom
Conversation
- User can set scrypt_n config option to control scrypt memory usage for better protection against brute-force attacks - Default remains 16384 (16MB) although I would recommend a way higher value in 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What is the purpose of this change?
Scrypt is a memory-hard key derivation algorithm but the current default value 16384 (16MB) is outdated and barely protects against modern GPU attacks. This commit makes the N parameter configurable to help protect against brute-force attacks. Default remains 16384 (16MB) although I would recommend a way higher value in 2026.
Was the change discussed in an issue or in the forum before?
No. It's a small, reasonable and optional change.
Checklist