keybase / keybase/keybase-issues
The manual workflow for verifying a public key fails on CSRF validation
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
After running the "verify my public key with curl + gpg" command, it spits out:
{"status":{"code":222,"desc":"CSRF-token verification failed for post","name":"CSRF"},"csrf_token":"..."}
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.
Research direction
Start by reproducing the manual “verify my public key with curl + gpg” workflow and inspect the returned CSRF error. Trace the verification request from that command to the server entry point; done means the documented workflow completes without CSRF-token verification failure.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100