In cryptography, the Elliptic Curve Digital Signature Algorithm (ECDSA) offers a variant of the Digital Signature Algorithm (DSA) which uses elliptic-curve cryptography.

Key and signature sizes

As with elliptic-curve cryptography in general, the bit size of the private key believed to be needed for ECDSA is about twice the size of the security level, in bits. For example, at a security level of 80 bits—meaning an attacker requires a maximum of about 2^{80} operations to find the private key—the size of an ECDSA private key would be 160 bits. On the other hand, the signature size is the same for both DSA and ECDSA: approximately 4 t bits, where t is the exponent in the formula 2^{t}, that is, about 320 bits for a security level of 80 bits, which is equivalent to 2^{80} operations.

Signature generation algorithm

Suppose Alice wants to send a signed message to Bob. Initially, they must agree on the curve parameters. In addition to the field and equation of the curve, we need G, a base point of prime order on the curve; n is the multiplicative order of the point G. The order n of the base point G must be prime. Indeed, we assume that every nonzero element of the ring is invertible, so that must be a field. It implies that n must be prime (cf. Bézout's identity). Alice creates a key pair, consisting of a private key integer d_A, randomly selected in the interval [1, n-1]; and a public key curve point. We use \times to denote elliptic curve point multiplication by a scalar. For Alice to sign a message m, she follows these steps: As the standard notes, it is not only required for k to be secret, but it is also crucial to select different k for different signatures. Otherwise, the equation in step 6 can be solved for d_A, the private key: given two signatures (r, s) and (r, s'), employing the same unknown k for different known messages m and m', an attacker can calculate z and z', and since (all operations in this paragraph are done modulo n) the attacker can find. Since, the attacker can now calculate the private key. This implementation failure was used, for example, to extract the signing key used for the PlayStation 3 gaming-console. Another way ECDSA signature may leak private keys is when k is generated by a faulty random number generator. Such a failure in random number generation caused users of Android Bitcoin Wallet to lose their funds in August 2013. To ensure that k is unique for each message, one may bypass random number generation completely and generate deterministic signatures by deriving k from both the message and the private key.

Signature verification algorithm

For Bob to authenticate Alice's signature r, s on a message m, he must have a copy of her public-key curve point Q_A. Bob can verify Q_A is a valid curve point as follows: After that, Bob follows these steps: Note that an efficient implementation would compute inverse only once. Also, using Shamir's trick, a sum of two scalar multiplications can be calculated faster than two scalar multiplications done independently.

Correctness of the algorithm

It is not immediately obvious why verification even functions correctly. To see why, denote as C the curve point computed in step 5 of verification, From the definition of the public key as , Because elliptic curve scalar multiplication distributes over addition, Expanding the definition of u_1 and u_2 from verification step 4, Collecting the common term s^{-1}, Expanding the definition of s from signature step 6, Since the inverse of an inverse is the original element, and the product of an element's inverse and the element is the identity, we are left with From the definition of r, this is verification step 6. This shows only that a correctly signed message will verify correctly; other properties such as incorrectly signed messages failing to verify correctly and resistance to cryptanalytic attacks are required for a secure signature algorithm.

Public key recovery

Given a message m and Alice's signature r, s on that message, Bob can (potentially) recover Alice's public key: Note that an invalid signature, or a signature from a different message, will result in the recovery of an incorrect public key. The recovery algorithm can only be used to check validity of a signature if the signer's public key (or its hash) is known beforehand.

Correctness of the recovery algorithm

Start with the definition of Q_A from recovery step 6, From the definition from signing step 4, Because elliptic curve scalar multiplication distributes over addition, Expanding the definition of u_1 and u_2 from recovery step 5, Expanding the definition of s from signature step 6, Since the product of an element's inverse and the element is the identity, we are left with The first and second terms cancel each other out, From the definition of, this is Alice's public key. This shows that a correctly signed message will recover the correct public key, provided additional information was shared to uniquely calculate curve point from signature value r.

Security

In December 2010, a group calling itself fail0verflow announced the recovery of the ECDSA private key used by Sony to sign software for the PlayStation 3 game console. However, this attack only worked because Sony did not properly implement the algorithm, because k was static instead of random. As pointed out in the Signature generation algorithm section above, this makes d_A solvable, rendering the entire algorithm useless. On March 29, 2011, two researchers published an IACR paper demonstrating that it is possible to retrieve a TLS private key of a server using OpenSSL that authenticates with Elliptic Curves DSA over a binary field via a timing attack. The vulnerability was fixed in OpenSSL 1.0.0e. In August 2013, it was revealed that bugs in some implementations of the Java class SecureRandom sometimes generated collisions in the k value. This allowed hackers to recover private keys giving them the same control over bitcoin transactions as legitimate keys' owners had, using the same exploit that was used to reveal the PS3 signing key on some Android app implementations, which use Java and rely on ECDSA to authenticate transactions. This issue can be prevented by deterministic generation of k, as described by RFC 6979.

Concerns

Some concerns expressed about ECDSA:

Implementations

Below is a list of cryptographic libraries that provide support for ECDSA: