letsencrypt / letsencrypt/boulder
Move bJSONWebSignature and constructor from wfe2 into a new package
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
The problem we want to solve here is, "Do we know where the bJSONWebSignature came from?" There's still going to be a potential mutability issue.
Contributor guide
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 reviewing the existing bJSONWebSignature and constructor in wfe2, then read the related pull request #6860 for context. Determine the intended new package boundary and how the design should answer where a signature came from while accounting for the noted mutability concern; done means the type and constructor are moved consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100