[cryptolib] Consider adding a keymgr API to read the maximum key version available.
Open
prodc-integration
SW:cryptolib
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
Currently, it takes time to debug side load errors triggered by invalid KMAC inputs in the keymgr. One way to mitigate this issue is by adding an API to check the maximum key version allowed by the keymgr.
Contributor guide
Research direction
Start by inspecting the keymgr API and the validation path for KMAC inputs that produces side-load errors. Trace how the maximum permitted key version is represented and tested; done means the keymgr exposes that maximum and coverage verifies the reported value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cryptography
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100