theupdateframework / theupdateframework/rust-tuf
Consider migrating signing to signatory
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
We are writing our own wrapper around boringssl instead of using ring, so it'd be nice to use our library for signing. One way to implementing this without forcing everyone to use the same crypto library would be to use signatory, which abstracts over a number of different libraries.
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 reading the existing wrapper around BoringSSL and reviewing signatory, linked in the issue, to compare their signing abstractions. Determine whether migrating to signatory can support multiple cryptographic libraries without forcing one implementation. Done means an agreed migration approach with its compatibility and scope clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100