lynndylanhurley / lynndylanhurley/devise_token_auth
Why BCrypt?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3.6k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
From what I could gather from the library code and docs the tokens are generated with a good source of entropy and do have a fixed lifestyle. Taking this into account wouldn't make more sense to use a fast hashing algorithm such as sha-2 ?
This would greatly lower the computational cost without any sacrifice of security. Or am I missing something?
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
The issue names no file, test, or entry point. Start by tracing token generation and BCrypt usage through the library code and documentation, then compare the security and lifecycle assumptions with SHA-2. Done would require an agreed scope and documented rationale before any implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100