Update BCryptPasswordEncoder documentation with default strength #8542
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.
Hi,
As mentioned in the Spring security doc on
BCryptPasswordEncoder
However, the default implementation of
BCryptPasswordEncoder
uses a default strength of 10.On my system (Intel Core i5 CPU-1.60Hz 8 GM RAM), I found that the default implementation takes around 220~250 ms to verify a password which is clearly way less than 1 second lower limit.
I think it should be worth mentioning the default strength of BCryptPasswordEncoder since all of the Spring projects I have worked with developers tend not to change the default strength which according to the Spring security doc is not secure.
This can make the developers using the default strength of
BCryptPasswordEncoder
more conscious about setting a correct secure strength.