The **ElGamal signature scheme** is a digital signature scheme which is based on the difficulty of computing discrete logarithms. It was described by Taher Elgamal in 1985.^{[1]}

The ElGamal signature algorithm is rarely used in practice. A variant developed at the NSA and known as the Digital Signature Algorithm is much more widely used. There are several other variants.^{[2]} The ElGamal signature scheme must not be confused with ElGamal encryption which was also invented by Taher Elgamal.

The ElGamal signature scheme is a digital signature scheme based on the algebraic properties of modular exponentiation, together with the discrete logarithm problem. The algorithm uses a **key pair** consisting of a **public key** and a **private key**. The private key is used to generate a **digital signature** for a message, and such a signature can be **verified** by using the signer's corresponding public key. The digital signature provides message authentication (the receiver can verify the origin of the message), integrity (the receiver can verify that the message has not been modified since it was signed) and non-repudiation (the sender cannot falsely claim that they have not signed the message).

The ElGamal signature scheme was described by Taher Elgamal in 1985.^{[1]}

The scheme involves four operations: key generation (which creates the key pair), key distribution, signing and signature verification.

Key generation has two phases. The first phase is a choice of algorithm parameters which may be shared between different users of the system, while the second phase computes a single key pair for one user.

- Choose a key length .
- Choose a -bit prime number
- Choose a cryptographic hash function with output length bits. If , only the leftmost bits of the hash output are used.
- Choose a generator of the multiplicative group of integers modulo
*p*, .

The algorithm parameters are . These parameters may be shared between users of the system.

Given a set of parameters, the second phase computes the key pair for a single user:

- Choose an integer randomly from .
- Compute .

is the private key and is the public key.

The signer should send the public key to the receiver via a reliable, but not necessarily secret, mechanism. The signer should keep the private key secret.

A message is signed as follows:

- Choose an integer randomly from with relatively prime to .
- Compute .
- Compute .
- In the unlikely event that start again with a different random .

The signature is .

One can verify that a signature is a valid signature for a message as follows:

- Verify that and .
- The signature is valid if and only if

The algorithm is correct in the sense that a signature generated with the signing algorithm will always be accepted by the verifier.

The computation of during signature generation implies

Since is relatively prime to ,

A third party can forge signatures either by finding the signer's secret key *x* or by finding collisions in the hash function . Both problems are believed to be difficult. However, as of 2011 no tight reduction to a computational hardness assumption is known.

The signer must be careful to choose a different *k* uniformly at random for each signature and to be certain that *k*, or even partial information about *k*, is not leaked. Otherwise, an attacker may be able to deduce the secret key *x* with reduced difficulty, perhaps enough to allow a practical attack. In particular, if two messages are sent using the same value of *k* and the same key, then an attacker can compute *x* directly.^{[1]}

The original paper^{[1]} did not include a hash function as a system parameter. The message *m* was used directly in the algorithm instead of *H(m)*. This enables an attack called existential forgery, as described in section IV of the paper. Pointcheval and Stern generalized that case and described two levels of forgeries:^{[3]}

**The one-parameter forgery.**Select an such that . Set and . Then the tuple is a valid signature for the message .**The two-parameters forgery.**Select , and . Set and . Then the tuple is a valid signature for the message . The one-parameter forgery is a special case of the two-parameter forgery, when .