Skip to content

FEAT | Support GPU resistent KDF in SecureConfig #71

New issue

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

Closed
sevenbitbyte opened this issue Apr 19, 2023 · 0 comments · Fixed by #73
Closed

FEAT | Support GPU resistent KDF in SecureConfig #71

sevenbitbyte opened this issue Apr 19, 2023 · 0 comments · Fixed by #73
Labels
enhancement New feature or request

Comments

@sevenbitbyte
Copy link
Member

sevenbitbyte commented Apr 19, 2023

🚀 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

  • GPU resistance
  • Evaluate argon2
  • Select specific argon2 algo (ie: argon2i vs argon2d vs argon2id)
  • Allow selection of various KDFs, though we should likely default to argon2 if possible.

NodeJS

Support native nodejs, consider node-argon2

Browser

Support browser, consider argon2-browser

Motivation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant