digitalbazaar / digitalbazaar/webkms-client
Consider adding a longer but still short lived (~5min) HMAC cache w/local-HMAC'd keys
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Some use cases that involve many repeated HMACs could benefit from a cache that performs a local HMAC on the value and stores it as a key in the cache. This local HMAC could use a newly generated key whenever the cache was created (e.g., on application start up).
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
The issue names no files, tests, or entry points. Start by locating the existing HMAC and cache implementation, then review how cache keys and cache lifetime are handled. Done means a short-lived cache can use a per-cache locally HMAC-derived key without exposing the original values, with tests covering repeated HMACs and expiry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100