We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
SecureConfig
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should use a more modern KDF which is GPU resistent.
A LUKs pbkdf2 partition was recently cracked using cloud services. (See Motivation 1)
1
It's recommended by cryptographers to use GPU resistent KDF functions such as argon2id. (See motivation 2)
argon2id
Our current SecureConfig class only supports pbkdf2, making it fairly vulnerable to GPU cracking attacks.
The initial breach disclosure can be seen in Motivation 3
3
argon2
argon2i
argon2d
Support native nodejs, consider node-argon2
node-argon2
Support browser, consider argon2-browser
argon2-browser
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Uh oh!
There was an error while loading. Please reload this page.
🚀 Feature Proposal
We should use a more modern KDF which is GPU resistent.
A LUKs pbkdf2 partition was recently cracked using cloud services. (See Motivation
1
)It's recommended by cryptographers to use GPU resistent KDF functions such as
argon2id
. (See motivation 2)Our current
SecureConfig
class only supports pbkdf2, making it fairly vulnerable to GPU cracking attacks.The initial breach disclosure can be seen in Motivation
3
Goals
argon2
argon2
algo (ie:argon2i
vsargon2d
vsargon2id
)argon2
if possible.NodeJS
Support native nodejs, consider
node-argon2
Browser
Support browser, consider
argon2-browser
Motivation
The text was updated successfully, but these errors were encountered: