Use peppered PBKDF2 for hosted Free deployment - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hosted authentication previously used scrypt that consumed 172–326 ms CPU in production probes, blocking a reliable Workers Free launch. Replace it with PBKDF2-SHA256 (100,000 iterations) followed by HMAC with a separate mandatory Cloudflare secret; preserve captcha, recovery codes and limits. Remove the paid-only CPU setting.
The operator accepted the lower offline guessing resistance if both database and pepper leak. Hosted D1 has zero existing users; legacy formats require recovery reset.
Validation: 115 tests, TypeScript, real local browser login/upload/sharing/device flows, Wrangler dry run, independent security review. Production CPU will be measured after deployment.