Open sseering opened 5 years ago
Neither the public, nor the secret key get modified by the signature generation operation; you can use the same SigningKey instance to sign as many different messages as needed in any order, and the same VerifyKey instance to check any number of messages signed by the corresponding SigningKey,
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?