Selection of algorithms
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- cryptography
Research direction
The issue lists DSA, binary elliptic curves, Morus, UMAC, and VMAC as primitives lacking clear use cases, but it names no files, tests, or implementation entry points. Start by reviewing the project's existing primitive test vectors and protocol coverage, then identify maintainer-approved use cases before deciding whether any new vectors should be added.
Written by the indexing model from the issue text.
Description
Another issue where opinions would be very useful is the selection of algorithms.
I have re-implemented most mainstream primitives and hence could continue adding test vectors for them. However, there are a number of algorithms for which I could not find any use cases anymore. Without use cases it makes little sense to spend time on them. The list of primitives that need some use cases are as follows:
- DSA (I haven't seen any use cases of DSA)
- binary elliptic curves (time is probably better spent adding newer curves used for cryptocurrencies)
- Morus (looks like a nice algorithms, I just haven't seen any use cases yet)
- UMAC
- VMAC
There are of course protocols that support cryptographic primitives for a long time, so maybe I'm overlooking something.
- Dominant language
- Go
- Stars
- 3.1k
- Forks
- 336
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from C2SP/wycheproof
-
json_web_signature_test.json: tcIds 357/367/370 are byte-identical with contradictory result labelsPossibly taken @sean0407 claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
C2SP/wycheproof#236 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
C2SP/wycheproof#275 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
C2SP/wycheproof#270 · 1 comment · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
C2SP/wycheproof#227 · 3 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
C2SP/wycheproof#212 · 2 comments ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
copilot-api domain:platform go
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
docs: clarify gh api -f vs -F and @-file expansion in the gh skillPossibly taken @MatiasOlivera claimed this today. Openenhancement
Difficulty 2/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws/aws-advanced-go-wrapper#612 ·
-
Say in the changelog that the text-index update cannot be rolled backPossibly taken @praetorianer777 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
praetorianer777/GoTome#275 ·
Maintainers usually reply within 1 day