mozilla-services / mozilla-services/autograph
server and client support alternate encodings
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 176
- Forks
- 34
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
i.e. avoid the base64 encode and decode for signing large files and possible the JSON part too.
This should be configurable per signer.
┆Issue is synchronized with this Jira Task
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 tracing the server and client signing paths to identify where base64 and JSON encoding are applied. Determine the supported alternate encodings and how per-signer configuration should represent them; done means large-file signing avoids the selected encodings while server and client remain compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100