Document if nacl.signing.SigningKey and VerifyKey can be reused.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 267
- Avg merge
- 42m
- Merged PRs (30d)
- 2
Description
The documentation should state if nacl.signing.SigningKey and VerifyKey objects can be used to sign/verify several messages with a keypair. Or does one need to create a new object for every message (like hmac and hashlib of the python standard library)?
From my testing it looks like one can reuse these object. Is this guaranteed in the future or just an deail of the current implementation?
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 with the documentation for nacl.signing.SigningKey and VerifyKey and compare it with the current reuse behavior described in the issue. Determine whether repeated signing and verification are supported guarantees, then document the answer and the expected object lifecycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cryptography, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100