-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Replace Argon2idPasswordEncoder by SodiumPasswordEncoder #31016
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
Comments
See #31019 |
fabpot
added a commit
that referenced
this issue
Apr 9, 2019
…swordEncoder (chalasr) This PR was merged into the 4.3-dev branch. Discussion ---------- [Security] Replace Argon2*PasswordEncoder by SodiumPasswordEncoder | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | yes | Tests pass? | yes | Fixed tickets | #31016 | License | MIT | Doc PR | todo symfony/symfony-docs#11368 See fixed ticket, much simpler/secure/maintainable. Commits ------- 529211d [Security] Replace Argon2*PasswordEncoder by SodiumPasswordEncoder
didnt happen (yet?) |
On it :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#31014 makes no sense to me: we added a class for which we cannot guarantee that it will work depending on a default that is under control of libsodium only.
To me this is the sign that we should adopt the approach of libsodium instead: we should replace
Argon2idPasswordEncoder
bySodiumPasswordEncoder
and align to its recommendation: trust them to always select the best default in the future. It's not like we have the choice: there is no other ways permitted by the extension (and I trust them on that it's the best).Similarly, I would add a new
NativePasswordEncoder
that would always usePASSWORD_DEFAULT
, and deprecateArgon2iPasswordEncoder
andBCryptPasswordEncoder
.The text was updated successfully, but these errors were encountered: