MoeraOrg / MoeraOrg/moera-issues
Use old signing key until the new becomes active
Open
Nobody has claimed this yet.
bug
good first issue
node
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
When user registers a new signing key, it becomes active since some moment of time in the future. Till that moment the node should use the old key for signing.
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 does not name a file, test, or entry point. Locate the code that registers signing keys and selects a key for signing, then inspect how the future activation time is handled. Done means signing continues with the old key until the new key becomes active, with coverage for both sides of that transition.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100