spring-projects / spring-projects/spring-security
SEC-2724: Password field is too small
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Per Holmberg (Migrated from SEC-2724) said:
As I have understood, BCrypt is now the recommended password encoder (or one of the recommended, at least). In the reference manual Appendix 1, the password field is defined as varchar_ignorecase(50), but that will not fit a bcrypt hash which normally is 60 characters. The field length should be at least 60.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reference manual's Appendix 1 and inspect the password field definition mentioned in the issue. Confirm the documented length against the stated 60-character BCrypt hash size; done means the field is documented as at least 60 characters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 40/100