Verify production laddr password-hash format before staging cutover
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- authentication
Research direction
Start with the laddr-import script and obtain the first approximately 20 Password values from a fresh production dump. Compare their algorithm prefixes; done means confirming a single format or recording the required verifier and warning in the account-claim plan and laddr-import report.
Written by the indexing model from the issue text.
Description
The laddr-import script writes legacy password hashes verbatim into LegacyPasswordCredential records, and the eventual account-claim endpoint will verify against them with whatever algorithm those hashes use.
Synthetic fixture data uses bcrypt (`$2y$10$...`) per common Emergence-PHP conventions, but we haven't inspected real production hashes yet. Before staging cutover:
- Pull the first ~20 `Password` values from a fresh production dump
- Confirm they all share a single algorithm prefix (`$2y$`, `$2a$`, `$6$`, etc.)
- If anything other than bcrypt appears, add a verifier in the account-claim plan and surface a warning in the import-laddr report
Filed as Follow-up from PR #24 (laddr-import).
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 25
Contributor guide
No contributing guide indexed for this repository
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.
More from CodeForPhilly/codeforphilly-ng
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
MarkdownEditor toolbar: use Radix Toolbar from radix-ui instead of the hand-rolled roving tabindex Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
All issues in CodeForPhilly/codeforphilly-ng
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·