Verify page: "Error: no header found"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
When inserting a saltpack signed message, it always gives this error.
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkDbcHiZ z1KmaVGP2MwDu8W IeOGWy46RgXq0vo vyO9lixKuQEJJ5b fHHInZJvGEdYcR1 LSOPcF4y6CV5Fta acr9eYCg7nsn5Zh wvmHAXhD07xJ25i fyH9kLZUBGheVJT 0xfAUDxiCpRViPm dGwZX8zQbjPfEFd mtzEA6WMqTdOGs1 . END KEYBASE SALTPACK SIGNED MESSAGE.
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
Reproduce the problem at https://keybase.io/verify using the saltpack signed message in the report. Trace how the verify page handles that input and identify why it reports “Error: no header found.” Done means the supplied signed message is handled correctly or the failure is reported with a clear, actionable result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100