General | |
---|---|

Designers | Ron Rivest, Adi Shamir, and Leonard Adleman |

First published | 1977 |

Certification | PKCS#1, ANSI X9.31, IEEE 1363 |

Cipher detail | |

Key sizes | 1,024 to 4,096 bit typical |

Rounds | 1 |

Best public cryptanalysis | |

General number field sieve for classical computers Shor's algorithm for quantum computers A 768-bit key has been broken |

**RSA** (**Rivest–Shamir–Adleman**) is one of the first public-key cryptosystems and is widely used for secure data transmission. In such a cryptosystem, the encryption key is public and it is different from the decryption key which is kept secret (private). In RSA, this asymmetry is based on the practical difficulty of the factorization of the product of two large prime numbers, the "factoring problem". The acronym RSA is made of the initial letters of the surnames of Ron Rivest, Adi Shamir, and Leonard Adleman, who first publicly described the algorithm in 1978. Clifford Cocks, an English mathematician working for the British intelligence agency Government Communications Headquarters (GCHQ), had developed an equivalent system in 1973, but this was not declassified until 1997.^{[1]}

A user of RSA creates and then publishes a public key based on two large prime numbers, along with an auxiliary value. The prime numbers must be kept secret. Anyone can use the public key to encrypt a message, but with currently published methods, and if the public key is large enough, only someone with knowledge of the prime numbers can decode the message feasibly.^{[2]}
Breaking RSA encryption is known as the RSA problem. Whether it is as difficult as the factoring problem remains an open question.

RSA is a relatively slow algorithm, and because of this, it is less commonly used to directly encrypt user data. More often, RSA passes encrypted shared keys for symmetric key cryptography which in turn can perform bulk encryption-decryption operations at much higher speed.

## Contents

## History

The idea of an asymmetric public-private key cryptosystem is attributed to Whitfield Diffie and Martin Hellman, who published this concept in 1976. They also introduced digital signatures and attempted to apply number theory. Their formulation used a shared-secret-key created from exponentiation of some number, modulo a prime number. However, they left open the problem of realizing a one-way function, possibly because the difficulty of factoring was not well-studied at the time.^{[3]}

Ron Rivest, Adi Shamir, and Leonard Adleman at the Massachusetts Institute of Technology made several attempts, over the course of a year, to create a one-way function that was hard to invert. Rivest and Shamir, as computer scientists, proposed many potential functions, while Adleman, as a mathematician, was responsible for finding their weaknesses. They tried many approaches including "knapsack-based" and "permutation polynomials". For a time, they thought what they wanted to achieve was impossible due to contradictory requirements.^{[4]} In April 1977, they spent Passover at the house of a student and drank a good deal of Manischewitz wine before returning to their homes at around midnight.^{[5]} Rivest, unable to sleep, lay on the couch with a math textbook and started thinking about their one-way function. He spent the rest of the night formalizing his idea, and he had much of the paper ready by daybreak. The algorithm is now known as RSA – the initials of their surnames in same order as their paper.^{[6]}

Clifford Cocks, an English mathematician working for the British intelligence agency Government Communications Headquarters (GCHQ), described an equivalent system in an internal document in 1973.^{[7]} However, given the relatively expensive computers needed to implement it at the time, RSA was considered to be mostly a curiosity and, as far as is publicly known, was never deployed. His discovery, however, was not revealed until 1997 due to its top-secret classification.

Kid-RSA (KRSA) is a simplified public-key cipher published in 1997, designed for educational purposes. Some people feel that learning Kid-RSA gives insight into RSA and other public-key ciphers, analogous to simplified DES.^{[8]}^{[9]}^{[10]}^{[11]}^{[12]}

## Patent

MIT was granted U.S. Patent 4,405,829 for a "Cryptographic communications system and method" that used the algorithm, on September 20, 1983. Though the patent was going to expire on September 21, 2000 (the term of patent was 17 years at the time), the algorithm was released to the public domain by RSA Security on September 6, 2000, two weeks earlier.^{[13]} Since a paper describing the algorithm had been published in August 1977,^{[6]} prior to the December 1977 filing date of the patent application, regulations in much of the rest of the world precluded patents elsewhere and only the US patent was granted. Had Cocks's work been publicly known, a patent in the United States would not have been legal either.

From the DWPI's abstract of the patent,

The system includes a communications channel coupled to at least one terminal having an encoding device and to at least one terminal having a decoding device. A message-to-be-transferred is enciphered to ciphertext at the encoding terminal by encoding the message as a number M in a predetermined set. That number is then raised to a first predetermined power (associated with the intended receiver) and finally computed. The remainder or residue, C, is... computed when the exponentiated number is divided by the product of two predetermined prime numbers (associated with the intended receiver).

## Operation

The RSA algorithm involves four steps: key generation, key distribution, encryption and decryption.

A basic principle behind RSA is the observation that it is practical to find three very large positive integers e, d and n such that with modular exponentiation for all integers m (with 0 ≤ *m* < *n*):

and that even knowing e and n or even m it can be extremely difficult to find d.

In addition, for some operations it is convenient that the order of the two exponentiations can be changed and that this relation also implies:

RSA involves a *public key* and a *private key.* The public key can be known by everyone, and it is used for encrypting messages. The intention is that messages encrypted with the public key can only be decrypted in a reasonable amount of time by using the private key. The public key is represented by the integers n and e; and, the private key, by the integer d (although n is also used during the decryption process. Thus, it might be considered to be a part of the private key, too). m represents the message (previously prepared with a certain technique explained below).

### Key generation

The keys for the RSA algorithm are generated the following way:

- Choose two distinct prime numbers
*p*and*q*.- For security purposes, the integers
*p*and*q*should be chosen at random, and should be similar in magnitude but differ in length by a few digits to make factoring harder.^{[2]}Prime integers can be efficiently found using a primality test.

- For security purposes, the integers
- Compute
*n*=*pq*.*n*is used as the modulus for both the public and private keys. Its length, usually expressed in bits, is the key length.

- Compute
*λ*(*n*) = lcm(*λ*(*p*),*λ*(*q*)) = lcm(*p*− 1,*q*− 1), where*λ*is Carmichael's totient function. This value is kept private. - Choose an integer
*e*such that 1 <*e*<*λ*(*n*) and gcd(*e*,*λ*(*n*)) = 1; i.e.,*e*and*λ*(*n*) are coprime. - Determine
*d*as*d*≡*e*^{−1}(mod*λ*(*n*)); i.e.,*d*is the modular multiplicative inverse of*e*modulo*λ*(*n*).

- This means: solve for
*d*the equation*d*⋅*e*≡ 1 (mod*λ*(*n*)). *e*having a short bit-length and small Hamming weight results in more efficient encryption – most commonly*e*= 2^{16}+ 1 = 65,537. However, much smaller values of*e*(such as 3) have been shown to be less secure in some settings.^{[14]}*e*is released as the public key exponent.*d*is kept as the private key exponent.

- This means: solve for

The *public key* consists of the modulus *n* and the public (or encryption) exponent *e*. The *private key* consists of the private (or decryption) exponent *d*, which must be kept secret. *p*, *q*, and *λ*(*n*) must also be kept secret because they can be used to calculate *d*.

In the original RSA paper,^{[2]} the Euler totient function *φ*(*n*) = (*p* − 1)(*q* − 1) is used instead of *λ*(*n*) for calculating the private exponent *d*. Since *φ*(*n*) is always divisible by *λ*(*n*) the algorithm works as well. That the Euler totient function can be used can also be seen as a consequence of the Lagrange's theorem applied to the multiplicative group of integers modulo pq. Thus any *d* satisfying *d*⋅*e* ≡ 1 (mod *φ*(*n*)) also satisfies *d*⋅*e* ≡ 1 (mod *λ*(*n*)). However, computing *d* modulo *φ*(*n*) will sometimes yield a result that is larger than necessary (i.e. *d* > *λ*(*n*)). Most of the implementations of RSA will accept exponents generated using either method (if they use the private exponent *d* at all, rather than using the optimized decryption method based on the Chinese remainder theorem described below), but some standards like FIPS 186-4 may require that *d* < *λ*(*n*). Any "oversized" private exponents not meeting that criterion may always be reduced modulo *λ*(*n*) to obtain a smaller equivalent exponent.

Since any common factors of (*p* − 1) and (*q* − 1) are present in the factorisation of *n* − 1 = *pq* − 1 = (*p* − 1)(*q* − 1) + (*p* − 1) + (*q* − 1),^{[15]} it is recommended that (*p* − 1) and (*q* − 1) have only very small common factors, if any besides the necessary 2.^{[2]}^{[16]}^{[17]}

Note: The authors of the original RSA paper carry out the key generation by choosing *d* and then computing *e* as the modular multiplicative inverse of *d* modulo *φ*(*n*). Since it is beneficial to use a small value for *e* (e.g., 65,537) in order to speed up the encryption function, current implementations of RSA, such as those following PKCS#1, choose *e* and compute *d* instead.^{[2]}^{[18]}

### Key distribution

Suppose that Bob wants to send information to Alice. If they decide to use RSA, Bob must know Alice's public key to encrypt the message and Alice must use her private key to decrypt the message.
To enable Bob to send his encrypted messages, Alice transmits her public key (*n*, *e*) to Bob via a reliable, but not necessarily secret, route. Alice's private key (*d*) is never distributed.

### Encryption

After Bob obtains Alice's public key, he can send a message M to Alice.

To do it, he first turns M (strictly speaking, the un-padded plaintext) into an integer m (strictly speaking, the padded plaintext), such that 0 ≤ *m* < *n* by using an agreed-upon reversible protocol known as a padding scheme. He then computes the ciphertext c, using Alice's public key e, corresponding to

This can be done reasonably quickly, even for 500-bit numbers, using modular exponentiation. Bob then transmits c to Alice.

### Decryption

Alice can recover m from c by using her private key exponent d by computing

Given m, she can recover the original message M by reversing the padding scheme.

### Example

Here is an example of RSA encryption and decryption. The parameters used here are artificially small, but one can also use OpenSSL to generate and examine a real keypair.

- Choose two distinct prime numbers, such as
- and

- Compute
*n*=*pq*giving - Compute the Carmichael's totient function of the product as
*λ*(*n*) = lcm(*p*− 1,*q*− 1) giving - Choose any number 1 <
*e*< 780 that is coprime to 780. Choosing a prime number for*e*leaves us only to check that*e*is not a divisor of 780.- Let

- Compute
*d*, the modular multiplicative inverse of*e*(mod*λ*(*n*)) yielding,- Worked example for the modular multiplicative inverse:

The **public key** is (*n* = 3233, *e* = 17). For a padded plaintext message *m*, the encryption function is

The **private key** is (*n* = 3233, *d* = 413). For an encrypted ciphertext *c*, the decryption function is

For instance, in order to encrypt *m* = 65, we calculate

To decrypt *c* = 2790, we calculate

Both of these calculations can be computed efficiently using the square-and-multiply algorithm for modular exponentiation. In real-life situations the primes selected would be much larger; in our example it would be trivial to factor *n*, 3233 (obtained from the freely available public key) back to the primes *p* and *q*. *e*, also from the public key, is then inverted to get *d*, thus acquiring the private key.

Practical implementations use the Chinese remainder theorem to speed up the calculation using modulus of factors (mod *pq* using mod *p* and mod *q*).

The values *d*_{p}, *d*_{q} and *q*_{inv}, which are part of the private key are computed as follows:

Here is how *d*_{p}, *d*_{q} and *q*_{inv} are used for efficient decryption. (Encryption is efficient by choice of a suitable *d* and *e* pair)

### Code

A working example in JavaScript using BigInteger.js. This code should not be used in production, as `bigInt.randBetween()`

uses `Math.random()`

, which is not a cryptographically secure pseudorandom number generator.^{[19]}

```
'use strict';
/**
* RSA hash function reference implementation.
* Uses BigInteger.js https://github.com/peterolson/BigInteger.js
* Code originally based on https://github.com/kubrickology/Bitcoin-explained/blob/master/RSA.js
*/
const RSA = {};
/**
* Generates a k-bit RSA public/private key pair
* https:/wiki/RSA_(cryptosystem)#Code
*
* @param {keysize} int, bitlength of desired RSA modulus n (should be even)
* @returns {array} Result of RSA generation (object with three bigInt members: n, e, d)
*/
RSA.generate = function(keysize) {
/**
* Generates a random k-bit prime greater than √2 × 2^(k-1)
*
* @param {bits} int, bitlength of desired prime
* @returns {bigInt} a random generated prime
*/
function randomPrime(bits) {
const min = bigInt(6074001000).shiftLeft(bits - 33); // min ≈ √2 × 2^(bits - 1)
const max = bigInt.one.shiftLeft(bits).minus(1); // max = 2^(bits) - 1
for (;;) {
const p = bigInt.randBetween(min, max); // WARNING: not a cryptographically secure RNG!
if (p.isProbablePrime(256)) {
return p;
}
}
}
// set up variables for key generation
const e = bigInt(65537); // use fixed public exponent
let p;
let q;
let lambda;
// generate p and q such that λ(n) = lcm(p − 1, q − 1) is coprime with e and |p-q| >= 2^(keysize/2 - 100)
do {
p = randomPrime(keysize / 2);
q = randomPrime(keysize / 2);
lambda = bigInt.lcm(p.minus(1), q.minus(1));
} while (bigInt.gcd(e, lambda).notEquals(1) || p.minus(q).abs().shiftRight(
keysize / 2 - 100).isZero());
return {
n: p.multiply(q), // public key (part I)
e: e, // public key (part II)
d: e.modInv(lambda), // private key d = e^(-1) mod λ(n)
};
};
/**
* Encrypt
*
* @param {m} int / bigInt: the 'message' to be encoded
* @param {n} int / bigInt: n value returned from RSA.generate() aka public key (part I)
* @param {e} int / bigInt: e value returned from RSA.generate() aka public key (part II)
* @returns {bigInt} encrypted message
*/
RSA.encrypt = function(m, n, e) {
return bigInt(m).modPow(e, n);
};
/**
* Decrypt
*
* @param {c} int / bigInt: the 'message' to be decoded (encoded with RSA.encrypt())
* @param {d} int / bigInt: d value returned from RSA.generate() aka private key
* @param {n} int / bigInt: n value returned from RSA.generate() aka public key (part I)
* @returns {bigInt} decrypted message
*/
RSA.decrypt = function(c, d, n) {
return bigInt(c).modPow(d, n);
};
```

### Signing messages

Suppose Alice uses Bob's public key to send him an encrypted message. In the message, she can claim to be Alice but Bob has no way of verifying that the message was actually from Alice since anyone can use Bob's public key to send him encrypted messages. In order to verify the origin of a message, RSA can also be used to sign a message.

Suppose Alice wishes to send a signed message to Bob. She can use her own private key to do so. She produces a hash value of the message, raises it to the power of *d* (modulo *n*) (as she does when decrypting a message), and attaches it as a "signature" to the message. When Bob receives the signed message, he uses the same hash algorithm in conjunction with Alice's public key. He raises the signature to the power of *e* (modulo *n*) (as he does when encrypting a message), and compares the resulting hash value with the message's actual hash value. If the two agree, he knows that the author of the message was in possession of Alice's private key, and that the message has not been tampered with since.

This works because multiplication is commutative so Thus, the keys may be swapped without loss of generality, that is a private key of a key pair may be used either to:

- Decrypt a message only intended for the recipient, which may be encrypted by anyone having the public key (asymmetric encrypted transport).
- Encrypt a message which may be decrypted by anyone, but which can only be encrypted by one person (signature).

## Proofs of correctness

### Proof using Fermat's little theorem

The proof of the correctness of RSA is based on Fermat's little theorem, stating that *a*^{p − 1} ≡ 1 (mod *p*) for any integer *a* and prime *p*, not dividing *a*.

We want to show that

for every integer *m* when *p* and *q* are distinct prime numbers and *e* and *d* are positive integers satisfying *ed* ≡ 1 (mod *λ*(*pq*)).

Since *λ*(*pq*) = lcm(*p* − 1, *q* − 1) is, by construction, divisible by both *p* − 1 and *q* − 1, we can write

for some nonnegative integers *h* and *k*.^{[note 1]}

To check whether two numbers, like *m ^{ed}* and

*m*, are congruent mod

*pq*, it suffices (and in fact is equivalent) to check that they are congruent mod

*p*and mod

*q*separately.

^{[note 2]}

To show *m ^{ed}* ≡

*m*(mod

*p*), we consider two cases:

- If
*m*≡ 0 (mod*p*),*m*is a multiple of*p*. Thus*m*is a multiple of^{ed}*p*. So*m*≡ 0 ≡^{ed}*m*(mod*p*). - If
*m*0 (mod*p*),

- where we used Fermat's little theorem to replace
*m*^{p−1}mod*p*with 1.

The verification that *m ^{ed}* ≡

*m*(mod

*q*) proceeds in a completely analogous way:

- If
*m*≡ 0 (mod*q*),*m*is a multiple of^{ed}*q*. So*m*≡ 0 ≡^{ed}*m*(mod*q*). - If
*m*0 (mod*q*),

This completes the proof that, for any integer *m*, and integers *e*, *d* such that *ed* ≡ 1 (mod *λ*(*pq*)),

*Notes:*

**^**In particular, the statement above holds for any*e*and*d*that satisfy*ed*≡ 1 (mod (*p*− 1)(*q*− 1)), since (*p*− 1)(*q*− 1) is divisible by*λ*(*pq*), and thus trivially also by*p*− 1 and*q*− 1. However, in modern implementations of RSA, it is common to use a reduced private exponent*d*that only satisfies the weaker but sufficient condition*ed*≡ 1 (mod*λ*(*pq*)).**^**This is part of the Chinese remainder theorem, although it is not the significant part of that theorem.

### Proof using Euler's theorem

Although the original paper of Rivest, Shamir, and Adleman used Fermat's little theorem to explain why RSA works, it is common to find proofs that rely instead on Euler's theorem.

We want to show that *m ^{ed}* ≡

*m*(mod

*n*), where

*n*=

*pq*is a product of two different prime numbers and

*e*and

*d*are positive integers satisfying

*ed*≡ 1 (mod

*φ*(

*n*)). Since

*e*and

*d*are positive, we can write

*ed*= 1 +

*hφ*(

*n*) for some non-negative integer

*h*.

*Assuming*that

*m*is relatively prime to

*n*, we have

where the second-last congruence follows from Euler's theorem.

More generally, for any *e* and *d* satisfying *ed* ≡ 1 (mod *λ*(*n*)), the same conclusion follows from Carmichael's generalization of Euler's theorem, which states that *m*^{λ(n)} ≡ 1 (mod *n*) for all *m* relatively prime to *n*.

When *m* is not relatively prime to *n*, the argument just given is invalid. This is highly improbable (only a proportion of 1/*p* + 1/*q* − 1/(*pq*) numbers have this property), but even in this case the desired congruence is still true. Either *m* ≡ 0 (mod *p*) or *m* ≡ 0 (mod *q*), and these cases can be treated using the previous proof.

## Padding

### Attacks against plain RSA

There are a number of attacks against plain RSA as described below.

- When encrypting with low encryption exponents (e.g.,
*e*= 3) and small values of the*m*, (i.e.,*m*<*n*^{1/e}) the result of*m*^{e}is strictly less than the modulus*n*. In this case, ciphertexts can be easily decrypted by taking the*e*th root of the ciphertext over the integers. - If the same clear text message is sent to
*e*or more recipients in an encrypted way, and the receivers share the same exponent*e*, but different*p*,*q*, and therefore*n*, then it is easy to decrypt the original clear text message via the Chinese remainder theorem. Johan Håstad noticed that this attack is possible even if the cleartexts are not equal, but the attacker knows a linear relation between them.^{[20]}This attack was later improved by Don Coppersmith.^{[21]}

- Because RSA encryption is a deterministic encryption algorithm (i.e., has no random component) an attacker can successfully launch a chosen plaintext attack against the cryptosystem, by encrypting likely plaintexts under the public key and test if they are equal to the ciphertext. A cryptosystem is called semantically secure if an attacker cannot distinguish two encryptions from each other, even if the attacker knows (or has chosen) the corresponding plaintexts. As described above, RSA without padding is not semantically secure.
^{[22]} - RSA has the property that the product of two ciphertexts is equal to the encryption of the product of the respective plaintexts. That is
*m*_{1}^{e}*m*_{2}^{e}≡ (*m*_{1}*m*_{2})^{e}(mod*n*). Because of this multiplicative property a chosen-ciphertext attack is possible. E.g., an attacker who wants to know the decryption of a ciphertext*c*≡*m*^{e}(mod*n*) may ask the holder of the private key*d*to decrypt an unsuspicious-looking ciphertext*c*′ ≡*cr*^{e}(mod*n*) for some value*r*chosen by the attacker. Because of the multiplicative property*c*′ is the encryption of*mr*(mod*n*). Hence, if the attacker is successful with the attack, he will learn*mr*(mod*n*) from which he can derive the message*m*by multiplying*mr*with the modular inverse of*r*modulo*n*.^{[citation needed]}

### Padding schemes

To avoid these problems, practical RSA implementations typically embed some form of structured, randomized padding into the value *m* before encrypting it. This padding ensures that *m* does not fall into the range of insecure plaintexts, and that a given message, once padded, will encrypt to one of a large number of different possible ciphertexts.

Standards such as PKCS#1 have been carefully designed to securely pad messages prior to RSA encryption. Because these schemes pad the plaintext *m* with some number of additional bits, the size of the un-padded message *M* must be somewhat smaller. RSA padding schemes must be carefully designed so as to prevent sophisticated attacks which may be facilitated by a predictable message structure. Early versions of the PKCS#1 standard (up to version 1.5) used a construction that appears to make RSA semantically secure. However, at Crypto 1998, Bleichenbacher showed that this version is vulnerable to a practical adaptive chosen ciphertext attack. Furthermore, at Eurocrypt 2000, Coron et al. showed that for some types of messages, this padding does not provide a high enough level of security. Later versions of the standard include Optimal Asymmetric Encryption Padding (OAEP), which prevents these attacks. As such, OAEP should be used in any new application, and PKCS#1 v1.5 padding should be replaced wherever possible. The PKCS#1 standard also incorporates processing schemes designed to provide additional security for RSA signatures, e.g. the Probabilistic Signature Scheme for RSA (RSA-PSS).

Secure padding schemes such as RSA-PSS are as essential for the security of message signing as they are for message encryption. Two US patents on PSS were granted (USPTO 6266771 and USPTO 70360140); however, these patents expired on 24 July 2009 and 25 April 2010, respectively. Use of PSS no longer seems to be encumbered by patents. Note that using different RSA key-pairs for encryption and signing is potentially more secure.^{[23]}

## Security and practical considerations

### Using the Chinese remainder algorithm

For efficiency many popular crypto libraries (like OpenSSL, Java and .NET) use the following optimization for decryption and signing based on the Chinese remainder theorem. The following values are precomputed and stored as part of the private key:

- and : the primes from the key generation,
- ,
- and
- .

These values allow the recipient to compute the exponentiation *m* = *c*^{d} (mod *pq*) more efficiently as follows:

- (if then some libraries compute
*h*as )

This is more efficient than computing exponentiation by squaring even though two modular exponentiations have to be computed. The reason is that these two modular exponentiations both use a smaller exponent and a smaller modulus.

### Integer factorization and RSA problem

The security of the RSA cryptosystem is based on two mathematical problems: the problem of factoring large numbers and the RSA problem. Full decryption of an RSA ciphertext is thought to be infeasible on the assumption that both of these problems are hard, i.e., no efficient algorithm exists for solving them. Providing security against *partial* decryption may require the addition of a secure padding scheme.^{[24]}

The RSA problem is defined as the task of taking *e*th roots modulo a composite *n*: recovering a value *m* such that *c* ≡ *m*^{e} (mod *n*), where (*n*, *e*) is an RSA public key and *c* is an RSA ciphertext. Currently the most promising approach to solving the RSA problem is to factor the modulus *n*. With the ability to recover prime factors, an attacker can compute the secret exponent *d* from a public key (*n*, *e*), then decrypt *c* using the standard procedure. To accomplish this, an attacker factors *n* into *p* and *q*, and computes lcm(*p* − 1, *q* − 1) which allows the determination of *d* from *e*. No polynomial-time method for factoring large integers on a classical computer has yet been found, but it has not been proven that none exists. *See integer factorization for a discussion of this problem*.

Multiple polynomial quadratic sieve (MPQS) can be used to factor the public modulus *n*. The time taken to factor 128-bit and 256-bit *n* on a desktop computer (Processor: Intel Dual-Core i7-4500U 1.80GHz) are respectively 2 seconds and 35 minutes.

Bits | Time |
---|---|

128 | Less than 2 seconds |

192 | 16 seconds |

256 | 35 minutes |

260 | 1 hour |

^{[original research?]}

A tool called YAFU can be used to optimize this process.^{[25]} It took about 5720s to factor *320bit-N* on the same computer.

Bits | Time | Memory used |
---|---|---|

128 | 0.4886 seconds | 0.1 MiB |

192 | 3.9979 seconds | 0.5 MiB |

256 | 103.1746 seconds | 3 MiB |

300 | 1175.7826 seconds | 10.9 MiB |

In 2009, Benjamin Moody factored an RSA-512 bit key in 73 days using only public software (GGNFS) and his desktop computer (a dual-core Athlon64 with a 1,900 MHz cpu.). Just less than five gigabytes of disk storage was required and about 2.5 gigabytes of RAM for the sieving process. The first RSA-512 factorization in 1999 required the equivalent of 8,400 MIPS years, over an elapsed time of about seven months.^{[26]}^{[better source needed]}

Rivest, Shamir, and Adleman noted^{[2]} that Miller has shown that – assuming the truth of the Extended Riemann Hypothesis – finding *d* from *n* and *e* is as hard as factoring *n* into *p* and *q* (up to a polynomial time difference).^{[27]} However, Rivest, Shamir, and Adleman noted, in section IX/D of their paper, that they had not found a proof that inverting RSA is equally as hard as factoring.

As of 2010^{[update]}, the largest factored RSA number was 768 bits long (232 decimal digits, see RSA-768). Its factorization, by a state-of-the-art distributed implementation, took around fifteen hundred CPU years (two years of real time, on many hundreds of computers). No larger RSA key is known publicly to have been factored. In practice, RSA keys are typically 1024 to 4096 bits long. Some experts believe that 1024-bit keys may become breakable in the near future or may already be breakable by a sufficiently well-funded attacker, though this is disputable. Few people see any way that 4096-bit keys could be broken in the foreseeable future. Therefore, it is generally presumed that RSA is secure if *n* is sufficiently large. If *n* is 300 bits or shorter, it can be factored in a few hours in a personal computer, using software already freely available. Keys of 512 bits have been shown to be practically breakable in 1999 when RSA-155 was factored by using several hundred computers, and these are now factored in a few weeks using common hardware. Exploits using 512-bit code-signing certificates that may have been factored were reported in 2011.^{[28]} A theoretical hardware device named TWIRL, described by Shamir and Tromer in 2003, called into question the security of 1024 bit keys. It is currently recommended that *n* be at least 2048 bits long.^{[29]}

In 1994, Peter Shor showed that a quantum computer – if one could ever be practically created for the purpose – would be able to factor in polynomial time, breaking RSA; see Shor's algorithm.

### Faulty key generation

This section needs additional citations for verification. (October 2017) (Learn how and when to remove this template message) |

Finding the large primes *p* and *q* is usually done by testing random numbers of the right size with probabilistic primality tests that quickly eliminate virtually all of the nonprimes.

The numbers *p* and *q* should not be "too close", lest the Fermat factorization for *n* be successful. If *p* − *q* is less than 2*n*^{1/4} (n = p * q, which for even small 1024-bit values of *n* is ×10^{77}) solving for 3*p* and *q* is trivial. Furthermore, if either *p* − 1 or *q* − 1 has only small prime factors, *n* can be factored quickly by Pollard's p − 1 algorithm, and such values of *p* or *q* should hence be discarded.

It is important that the private exponent *d* be large enough. Michael J. Wiener showed that if *p* is between *q* and 2*q* (which is quite typical) and *d* < *n*^{1/4}/3, then *d* can be computed efficiently from *n* and *e*.^{[30]}

There is no known attack against small public exponents such as *e* = 3, provided that the proper padding is used. Coppersmith's Attack has many applications in attacking RSA specifically if the public exponent *e* is small and if the encrypted message is short and not padded. 65537 is a commonly used value for *e*; this value can be regarded as a compromise between avoiding potential small exponent attacks and still allowing efficient encryptions (or signature verification). The NIST Special Publication on Computer Security (SP 800-78 Rev 1 of August 2007) does not allow public exponents *e* smaller than 65537, but does not state a reason for this restriction.

In October 2017 a team of researchers from Masaryk University announced the ROCA vulnerability, which affects RSA keys generated by an algorithm embodied in a library from Infineon. Large number of smart cards and TPMs were shown to be affected. Vulnerable RSA keys are easily identified using a test program the team released.^{[31]}

### Importance of strong random number generation

A cryptographically strong random number generator, which has been properly seeded with adequate entropy, must be used to generate the primes *p* and *q*. An analysis comparing millions of public keys gathered from the Internet was carried out in early 2012 by Arjen K. Lenstra, James P. Hughes, Maxime Augier, Joppe W. Bos, Thorsten Kleinjung and Christophe Wachter. They were able to factor 0.2% of the keys using only Euclid's algorithm.^{[32]}^{[33]}

They exploited a weakness unique to cryptosystems based on integer factorization. If *n* = *pq* is one public key and *n*′ = *p*′*q*′ is another, then if by chance *p* = *p*′ (but q is not equal to q'), then a simple computation of gcd(*n*,*n*���) = *p* factors both *n* and *n*′, totally compromising both keys. Lenstra et al. note that this problem can be minimized by using a strong random seed of bit-length twice the intended security level, or by employing a deterministic function to choose *q* given *p*, instead of choosing *p* and *q* independently.

Nadia Heninger was part of a group that did a similar experiment. They used an idea of Daniel J. Bernstein to compute the GCD of each RSA key *n* against the product of all the other keys *n*′ they had found (a 729 million digit number), instead of computing each gcd(*n*,*n*′) separately, thereby achieving a very significant speedup since after one large division the GCD problem is of normal size.

Heninger says in her blog that the bad keys occurred almost entirely in embedded applications, including "firewalls, routers, VPN devices, remote server administration devices, printers, projectors, and VOIP phones" from over 30 manufacturers. Heninger explains that the one-shared-prime problem uncovered by the two groups results from situations where the pseudorandom number generator is poorly seeded initially and then reseeded between the generation of the first and second primes. Using seeds of sufficiently high entropy obtained from key stroke timings or electronic diode noise or atmospheric noise from a radio receiver tuned between stations should solve the problem.^{[34]}

Strong random number generation is important throughout every phase of public key cryptography. For instance, if a weak generator is used for the symmetric keys that are being distributed by RSA, then an eavesdropper could bypass RSA and guess the symmetric keys directly.

### Timing attacks

Kocher described a new attack on RSA in 1995: if the attacker Eve knows Alice's hardware in sufficient detail and is able to measure the decryption times for several known ciphertexts, she can deduce the decryption key *d* quickly. This attack can also be applied against the RSA signature scheme. In 2003, Boneh and Brumley demonstrated a more practical attack capable of recovering RSA factorizations over a network connection (e.g., from a Secure Sockets Layer (SSL)-enabled webserver)^{[35]} This attack takes advantage of information leaked by the Chinese remainder theorem optimization used by many RSA implementations.

One way to thwart these attacks is to ensure that the decryption operation takes a constant amount of time for every ciphertext. However, this approach can significantly reduce performance. Instead, most RSA implementations use an alternate technique known as cryptographic blinding. RSA blinding makes use of the multiplicative property of RSA. Instead of computing *c*^{d} (mod *n*), Alice first chooses a secret random value *r* and computes (*r*^{e}*c*)^{d} (mod *n*). The result of this computation after applying Euler's Theorem is *rc*^{d} (mod *n*) and so the effect of *r* can be removed by multiplying by its inverse. A new value of *r* is chosen for each ciphertext. With blinding applied, the decryption time is no longer correlated to the value of the input ciphertext and so the timing attack fails.

### Adaptive chosen ciphertext attacks

In 1998, Daniel Bleichenbacher described the first practical adaptive chosen ciphertext attack, against RSA-encrypted messages using the PKCS #1 v1 padding scheme (a padding scheme randomizes and adds structure to an RSA-encrypted message, so it is possible to determine whether a decrypted message is valid). Due to flaws with the PKCS #1 scheme, Bleichenbacher was able to mount a practical attack against RSA implementations of the Secure Socket Layer protocol, and to recover session keys. As a result of this work, cryptographers now recommend the use of provably secure padding schemes such as Optimal Asymmetric Encryption Padding, and RSA Laboratories has released new versions of PKCS #1 that are not vulnerable to these attacks.

### Side-channel analysis attacks

A side-channel attack using branch prediction analysis (BPA) has been described. Many processors use a branch predictor to determine whether a conditional branch in the instruction flow of a program is likely to be taken or not. Often these processors also implement simultaneous multithreading (SMT). Branch prediction analysis attacks use a spy process to discover (statistically) the private key when processed with these processors.

Simple Branch Prediction Analysis (SBPA) claims to improve BPA in a non-statistical way. In their paper, "On the Power of Simple Branch Prediction Analysis",^{[36]} the authors of SBPA (Onur Aciicmez and Cetin Kaya Koc) claim to have discovered 508 out of 512 bits of an RSA key in 10 iterations.

A power fault attack on RSA implementations has been described in 2010.^{[37]} The author recovered the key by varying the CPU power voltage outside limits; this caused multiple power faults on the server.

## Implementations

Below are some cryptography libraries that provide support for RSA:

## See also

- Acoustic cryptanalysis
- Computational complexity theory
- Cryptographic key length
- Diffie–Hellman key exchange
- Key exchange
- Key management
- Public-key cryptography
- Trapdoor function

## References

**^**Smart, Nigel (February 19, 2008). "Dr Clifford Cocks CB". Bristol University. Retrieved August 14, 2011.- ^
^{a}^{b}^{c}^{d}^{e}^{f}Rivest, R.; Shamir, A.; Adleman, L. (February 1978). "A Method for Obtaining Digital Signatures and Public-Key Cryptosystems" (PDF).*Communications of the ACM*.**21**(2): 120–126. doi:10.1145/359340.359342. **^**Diffie, W.; Hellman, M.E. (November 1976). "New directions in cryptography".*IEEE Transactions on Information Theory*.**22**(6): 644–654. doi:10.1109/TIT.1976.1055638. ISSN 0018-9448.**^**Rivest, Ronald. "The Early Days of RSA -- History and Lessons" (PDF).**^**Calderbank, Michael (2007-08-20). "The RSA Cryptosystem: History, Algorithm, Primes" (PDF).- ^
^{a}^{b}Robinson, Sara (June 2003). "Still Guarding Secrets after Years of Attacks, RSA Earns Accolades for its Founders" (PDF).*SIAM News*.**36**(5). **^**Cocks, C.C. (20 November 1973). "A Note on Non-Secret Encryption" (PDF).*www.gchq.gov.uk*. Retrieved 2017-05-30.**^**Jim Sauerberg "From Private to Public Key Ciphers in Three Easy Steps".**^**Margaret Cozzens and Steven J. Miller. "The Mathematics of Encryption: An Elementary Introduction". p. 180.**^**Alasdair McAndrew. "Introduction to Cryptography with Open-Source Software". p. 12.**^**Surender R. Chiluka. "Public key Cryptography".**^**Neal Koblitz. "Cryptography As a Teaching Tool". Cryptologia, Vol. 21, No. 4 (1997).**^**"RSA Security Releases RSA Encryption Algorithm into Public Domain". Archived from the original on June 21, 2007. Retrieved 2010-03-03.**^**Boneh, Dan (1999). "Twenty Years of attacks on the RSA Cryptosystem".*Notices of the American Mathematical Society*.**46**(2): 203–213.**^**"Further Attacks ON Server-Aided RSA Cryptosystems", James McKee and Richard Pinch, http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.33.1333**^**A Course in Number Theory and Cryptography, Graduate Texts in Math. No. 114, Springer-Verlag, New York, 1987. Neal Koblitz, Second edition, 1994. p. 94**^**"common factors in (*p*− 1) and (*q*− 1)",Viktor Dukhovni, openssl-dev Digest, Vol 9, Issue 4, https://www.mail-archive.com/openssl-dev%40openssl.org/msg39736.html, https://www.mail-archive.com/openssl-dev%40openssl.org/msg39725.html**^**Johnson, J.; Kaliski, B. (February 2003). "Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1".*www.ietf.org*. Network Working Group. Retrieved 9 March 2016.**^**Scholz, Florian; Shepherd, Eric. "Math.random()".*Mozilla Developer Network*. Retrieved 5 June 2016.**^**Håstad, Johan (1986). "On using RSA with Low Exponent in a Public Key Network".*Advances in Cryptology — CRYPTO ’85 Proceedings*. Lecture Notes in Computer Science.**218**. pp. 403–408. doi:10.1007/3-540-39799-X_29.**^**Coppersmith, Don (1997). "Small Solutions to Polynomial Equations, and Low Exponent RSA Vulnerabilities" (PDF).*Journal of Cryptology*.**10**(4): 233–260. doi:10.1007/s001459900030.**^**S. Goldwasser and S. Micali, Probabilistic encryption & how to play mental poker keeping secret all partial information, Annual ACM Symposium on Theory of Computing, 1982.**^**https://www.di-mgt.com.au/rsa_alg.html#weaknesses**^**Edmond K. Machie. "NETWORK SECURITY TRACEBACK ATTACK AND REACT IN THE UNITED STATES DEPARTMENT". p. 167.**^**https://sourceforge.net/projects/yafu/**^**http://lukenotricks.blogspot.se/2009/08/solo-desktop-factorization-of-rsa-512.html**^**Gary L. Miller, "Riemann's Hypothesis and Tests for Primality"**^**RSA-512 certificates abused in-the-wild**^**Has the RSA algorithm been compromised as a result of Bernstein's Paper? What key size should I be using?**^**Wiener, Michael J. (May 1990). "Cryptanalysis of short RSA secret exponents" (PDF).*Information Theory, IEEE Transactions on*.**36**(3): 553–558. doi:10.1109/18.54902.**^**The Return of Coppersmith’s Attack: Practical Factorization of Widely Used RSA Moduli, Matus Nemec, Marek Sys, Petr Svenda, Dusan Klinec,Vashek Matyas, November 2017**^**Markoff, John (February 14, 2012). "Flaw Found in an Online Encryption Method".*The New York Times*.**^**"Ron was wrong, Whit is right" (PDF).**^**https://freedom-to-tinker.com/blog/nadiah/new-research-theres-no-need-panic-over-factorable-keys-just-mind-your-ps-and-qs**^**Remote timing attacks are practical. . SSYM'03 Proceedings of the 12th conference on USENIX Security Symposium.**^**http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.80.1438&rep=rep1&type=pdf**^**FaultBased Attack of RSA Authentication

## Further reading

- Menezes, Alfred; van Oorschot, Paul C.; Vanstone, Scott A. (October 1996).
*Handbook of Applied Cryptography*. CRC Press. ISBN 0-8493-8523-7. - Cormen, Thomas H.; Leiserson, Charles E.; Rivest, Ronald L.; Stein, Clifford (2001).
*Introduction to Algorithms*(2nd ed.). MIT Press and McGraw-Hill. pp. 881–887. ISBN 0-262-03293-7.

## External links

- The Original RSA Patent as filed with the U.S. Patent Office by Rivest; Ronald L. (Belmont, MA), Shamir; Adi (Cambridge, MA), Adleman; Leonard M. (Arlington, MA), December 14, 1977,
**U.S. Patent 4,405,829**. - PKCS #1: RSA Cryptography Standard (RSA Laboratories website)
- The
*PKCS #1*standard*"provides recommendations for the implementation of public-key cryptography based on the*.**RSA**algorithm, covering the following aspects: cryptographic primitives; encryption schemes; signature schemes with appendix; ASN.1 syntax for representing keys and for identifying the schemes"

- The
- Explanation of RSA using colored lamps on YouTube
- Thorough walk through of RSA
- Prime Number Hide-And-Seek: How the RSA Cipher Works
- Onur Aciicmez, Cetin Kaya Koc, Jean-Pierre Seifert:
*On the Power of Simple Branch Prediction Analysis* - A New Vulnerability In RSA Cryptography, CAcert NEWS Blog
- Example of an RSA implementation with PKCS#1 padding (GPL source code)
- Kocher's article about timing attacks
- An animated explanation of RSA with its mathematical background by CrypTool
*Hacking Secret Ciphers with Python*, Chapter 24, Public Key Cryptography and the RSA Cipher- Grime, James. "RSA Encryption".
*Numberphile*. Brady Haran. - How RSA Key used for Encryption in real world