为什么Node.js的crypto.sign函数具有非确定性？

Great question! The non-deterministic behavior you're seeing is actually by design for ECDSA (Elliptic Curve Digital Signature Algorithm)—and Node.js's crypto module is following secure cryptographic best practices here. Let me break this down:

1. ECDSA requires a random ephemeral key (k) #

ECDSA signatures rely on a temporary, randomly generated private key called k (ephemeral key) during the signing process. This value is unique per signature:

• Every time you generate a signature, a new random k is created.
• The final signature consists of two values, r and s, which are derived from k, your private key, and the message hash.
• Since k changes every time, r and s (and thus the final hex signature) will also change—even for the same message and private key.

This isn't a bug! Reusing the same k for multiple signatures would expose your private key to attackers (a well-known vulnerability in ECDSA), so randomizing k is critical for security.

2. How to get deterministic ECDSA signatures (if you need them) #

If you require consistent signatures for the same message (e.g., for testing or specific use cases), you can use deterministic ECDSA as defined in RFC 6979. This standard generates k deterministically from the message hash and your private key, eliminating randomness while maintaining security.

To enable this in Node.js, pass the rfc6979: true option when calling sign():

function signIt() {
  const sign = crypto.createSign('SHA256');
  sign.update(message);
  // Enable RFC 6979 deterministic signing
  console.log(sign.sign({ key: key, rfc6979: true }, 'hex'));
}

With this change, running your loop 10 times will output the exact same signature every time.

3. A quick note on validation #

Regardless of whether you use random or deterministic k, all generated signatures will be valid when verified with your public key. Both approaches produce legitimate ECDSA signatures—they just differ in how k is generated.

内容的提问来源于stack exchange，提问作者Otavio Macedo