Template:About In cryptography, RSA (which stands for Rivest, Shamir and Adleman who first publicly described it) is an algorithm for publickey cryptography.^{[1]} It is the first algorithm known to be suitable for signing as well as encryption, and was one of the first great advances in public key cryptography. RSA is widely used in electronic commerce protocols, and is believed to be secure given sufficiently long keys and the use of uptodate implementations.
History[]
Clifford Cocks, a British mathematician working for the UK intelligence agency GCHQ, described an equivalent system in an internal document in 1973, but given the relatively expensive computers needed to implement it at the time, it was mostly considered a curiosity and, as far as is publicly known, was never deployed. His discovery, however, was not revealed until 1998 due to its topsecret classification, and Rivest, Shamir, and Adleman devised RSA independently of Cocks' work.
The RSA algorithm was publicly described in 1978 by Ron Rivest, Adi Shamir, and Leonard Adleman at MIT; the letters RSA are the initials of their surnames, listed in the same order as on the paper.^{[2]}
MIT was granted Template:US patent for a "Cryptographic communications system and method" that used the algorithm in 1983. The patent would have expired on September 21, 2000 (the term of patent was 17 years at the time), but the algorithm was released to the public domain by RSA Security on 6 September 2000, two weeks earlier.^{[3]} Since a paper describing the algorithm had been published in August 1977,^{[2]} 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' work been publicly known, a patent in the US might not have been possible.
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 messagetobetransferred 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 three steps: key generation, encryption and decryption.
Key generation[]
RSA involves a public key and a private key. The public key can be known to everyone and is used for encrypting messages. Messages encrypted with the public key can only be decrypted using the private key. The keys for the RSA algorithm are generated the following way:
 Choose two distinct prime numbers and .
 For security purposes, the integers and should be chosen uniformly at random and should be of similar bitlength. Prime integers can be efficiently found using a primality test.
 Compute .
 is used as the modulus for both the public and private keys
 Compute . ( is Euler's totient function).
 Choose an integer such that , and (i.e., and are coprime).
 is released as the public key exponent.
 having a short bitlength and small Hamming weight results in more efficient encryption  most commonly 0x10001 = 65537. However, small values of (such as ) have been shown to be less secure in some settings.^{[4]}
 Determine (using Modular multiplicative inverse). This satisfies the congruence relation .
 Stated differently, .
 This is often computed using the Modular multiplicative inverse and extended Euclidean algorithm.
 is kept as the private key exponent.
The public key consists of the modulus and the public (or encryption) exponent . The private key consists of the private (or decryption) exponent which must be kept secret.
Note:
 An alternative, used by PKCS#1, is to choose matching with , where is the least common multiple. Using instead of allows more choices for . can also be defined using the Carmichael function, .
Encryption[]
Alice transmits her public key to Bob and keeps the private key secret. Bob then wishes to send message M to Alice.
He first turns M into an integer by using an agreedupon reversible protocol known as a padding scheme. He then computes the ciphertext corresponding to:
This can be done quickly using the method of exponentiation by squaring. Bob then transmits to Alice.
Decryption[]
Alice can recover from by using her private key exponent by the following computation:
Given , she can recover the original message M by reversing the padding scheme.
(In practice, there are more efficient methods of calculating c^{d} using the pre computed values above.)
A worked 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 prime numbers
 and Make sure that these prime numbers are distinct (i.e. they are not both the same number).
 Compute
 Compute the totients of product. For primes the totient is maximal and equals the prime minus one. Therefore
 Choose any number that is coprime to 3120. Choosing a prime number for leaves you with a single check: that is not a divisor of 3120.
 Compute such that e.g., by computing the modular multiplicative inverse of modulo :
 since 17 · 2753 = 46801 and 46801 mod 3120 = 1, this is the correct answer.
 (iterating finds (15 times 3120)+1 divided by 17 is 2753, an integer, whereas other values in place of 15 do not produce an integer. The extended euclidean algorithm finds the solution to Bézout's identity of 3120x2 + 17x367=1, and 367 mod 3120 is 2753)
The public key is (, ). For a padded plaintext message , the encryption function is or abstractly:
The private key is (, ). For an encrypted ciphertext , the decryption function is or in its general form:
For instance, in order to encrypt , we calculate
To decrypt , we calculate
 .
Both of these calculations can be computed efficiently using the squareandmultiply algorithm for modular exponentiation. In real life situations the primes selected would be much larger; in our example it would be relatively trivial to factor , 3233, obtained from the freely available public key back to the primes and . Given , also from the public key, we could then compute and so acquire the private key.
Using the Chinese remainder algorithm[]
For efficiency many popular crypto libraries (like OpenSSL, Java and .NET) use the following optimization for decryption and signing: The following values are precomputed and stored as part of the private key:
 and : the primes from the key generation,
 ,
 and
 .
These values allow to compute the exponentiation more efficiently computed as follows:
 (if then some libraries compute h as )
This is more efficient than computing 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.
Attacks against plain RSA[]
There are a number of attacks against plain RSA as described above.
 When encrypting with low encryption exponents (e.g., ) and small values of the , (i.e. ) the result of is strictly less than the modulus . In this case, ciphertexts can be easily decrypted by taking the th root of the ciphertext over the integers.
 If the same clear text message is sent to or more recipients in an encrypted way, and the receivers share the same exponent , but different , , and , 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.^{[5]} This attack was later improved by Don Coppersmith.^{[6]}
 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.
 RSA has the property that the product of two ciphertexts is equal to the encryption of the product of the respective plaintexts. That is Because of this multiplicative property a chosenciphertext attack is possible. E.g. an attacker, who wants to know the decryption of a ciphertext may ask the holder of the private key to decrypt an unsuspiciouslooking ciphertext for some value chosen by the attacker. Because of the multiplicative property is the encryption of . Hence, if the attacker is successful with the attack, he will learn from which he can derive the message m by multiplying with the modular inverse of modulo .
Padding schemes[]
To avoid these problems, practical RSA implementations typically embed some form of structured, randomized padding into the value before encrypting it. This padding ensures that 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 with some number of additional bits, the size of the unpadded 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 turned RSA into a semantically secure encryption scheme. This version was later found vulnerable to a practical adaptive chosen ciphertext attack. Later versions of the standard include Optimal Asymmetric Encryption Padding (OAEP), which prevents these attacks. The PKCS#1 standard also incorporates processing schemes designed to provide additional security for RSA signatures, e.g., the Probabilistic Signature Scheme for RSA (RSAPSS).
In the common case where RSA is used to exchange symmetric keys, key encapsulation provides a simpler alternative to padding. Instead of generating a random symmetric key, padding it and then encrypting the padded version with RSA, a random integer m between 1 and n1 is generated and encrypted directly using RSA. Both the sender and receiver generate identical symmetric keys by applying the same key derivation function to m.^{[7]}
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 (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 (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.
Note that secure padding schemes such as RSAPSS are as essential for the security of message signing as they are for message encryption, and that the same key should never be used for both encryption and signing purposes^{[8]}.
Security and practical considerations[]
Integer factorization and RSA problem[]
Template:See also 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.Template:Citation needed
The RSA problem is defined as the task of taking th roots modulo a composite : recovering a value such that , where is an RSA public key and is an RSA ciphertext. Currently the most promising approach to solving the RSA problem is to factor the modulus . With the ability to recover prime factors, an attacker can compute the secret exponent from a public key , then decrypt using the standard procedure. To accomplish this, an attacker factors into and , and computes which allows the determination of from . No polynomialtime 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. Rivest, Shamir and Adleman have shown that finding d from n and e is equally hard as factoring n into p and q^{[1]}. However, this proof does not imply that inverting RSA is equally hard as factoring.
As of 2010 , the largest (known) number factored by a generalpurpose factoring algorithm was 768 bits long (see RSA768), using a stateoftheart distributed implementation. RSA keys are typically 1024–2048 bits long. Some experts believe that 1024bit keys may become breakable in the near term (though this is disputed); few see any way that 4096bit keys could be broken in the foreseeable future. Therefore, it is generally presumed that RSA is secure if is sufficiently large. If is 300 bits or shorter, it can be factored in a few hours on a personal computer, using software already freely available. Keys of 512 bits have been shown to be practically breakable in 1999 when RSA155 was factored by using several hundred computers and are now factored in a few weeks using common hardware.^{[9]} A theoretical hardware device named TWIRL and described by Shamir and Tromer in 2003 called into question the security of 1024 bit keys. It is currently recommended that be at least 2048 bits long.^{[10]}
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.
Key generation[]
Finding the large primes p and q is usually done by testing random numbers of the right size with probabilistic primality tests which quickly eliminate virtually all nonprimes.
Numbers p and q should not be 'too close', lest the Fermat factorization for n be successful, if p − q, for instance is less than 2n^{1/4} (which for even small 1024bit values of n is 3×10^{77}) solving for 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 these values of p or q should therefore be discarded as well.
It is important that the private key d be large enough. Michael J. Wiener showed^{[11]} that if p is between q and 2q (which is quite typical) and d < n^{1/4}/3, then d can be computed efficiently from n and e. There is no known attack against small public exponents such as e = 3, provided that proper padding is used. However, when no padding is used or when the padding is improperly implemented then small public exponents have a greater risk of leading to an attack, such as for example the unpadded plaintext vulnerability listed above. 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 80078 Rev 1 of August 2007) does not allow public exponents e smaller than 65537, but does not state a reason for this restriction.
Speed[]
RSA is much slower than DES and other symmetric cryptosystems. In practice, Bob typically encrypts a secret message with a symmetric algorithm, encrypts the (comparatively short) symmetric key with RSA, and transmits both the RSAencrypted symmetric key and the symmetricallyencrypted message to Alice.
This procedure raises additional security issues. For instance, it is of utmost importance to use a strong random number generator for the symmetric key, because otherwise Eve (an eavesdropper wanting to see what was sent) could bypass RSA by guessing the symmetric key.
Key distribution[]
As with all ciphers, how RSA public keys are distributed is important to security. Key distribution must be secured against a maninthemiddle attack. Suppose Eve has some way to give Bob arbitrary keys and make him believe they belong to Alice. Suppose further that Eve can intercept transmissions between Alice and Bob. Eve sends Bob her own public key, which Bob believes to be Alice's. Eve can then intercept any ciphertext sent by Bob, decrypt it with her own private key, keep a copy of the message, encrypt the message with Alice's public key, and send the new ciphertext to Alice. In principle, neither Alice nor Bob would be able to detect Eve's presence. Defenses against such attacks are often based on digital certificates or other components of a public key infrastructure.
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 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 Socket Layer (SSL)enabled webserver). 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 , Alice first chooses a secret random value and computes . The result of this computation after applying Euler's Theorem is and so the effect of can be removed by multiplying by its inverse. A new value of 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 RSAencrypted messages using the PKCS #1 v1 padding scheme (a padding scheme randomizes and adds structure to an RSAencrypted 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.
Sidechannel analysis attacks[]
A sidechannel 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 nonstatistical way. In their paper, "On the Power of Simple Branch Prediction Analysis"^{[12]}, 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^{[13]}.
Proofs of correctness[]
Concise proof[]
To show that a message encrypted with e can be decrypted with d we need to prove
i.e.
Now, since ,
The last congruence directly follows from Euler's theorem when is relatively prime to . It can be shown that the equations holds for all using congruency arguments and the Chinese remainder theorem.
More intuitive derivation[]
Another way to prove the correctness of RSA is based on Fermat's little theorem. This theorem states that if p is prime and p does not divide a then
In RSA, the modulus is a product of two primes p and q. The public key e and private key d satisfy
Therefore, there exists an integer h, such that
We can then continue to calculate
And likewise for q
If p and q are coprime, and then the Chinese remainder theorem implies . Hence
See also[]
 Encryption
 Key exchange
 DiffieHellman key exchange
 Key management
 Cryptographic key length
 Computational complexity theory
Notes[]
 ↑ ^{1.0} ^{1.1} Template:Cite journal
 ↑ ^{2.0} ^{2.1} SIAM News, Volume 36, Number 5, June 2003, "Still Guarding Secrets after Years of Attacks, RSA Earns Accolades for its Founders", by Sara Robinson
 ↑ http://www.rsa.com/press_release.aspx?id=261
 ↑ Template:Cite journal
 ↑ Johan Håstad, "On using RSA with Low Exponent in a Public Key Network", Crypto 85
 ↑ Don Coppersmith, "Small Solutions to Polynomial Equations, and Low Exponent RSA Vulnerabilities", Journal of Cryptology, v. 10, n. 4, Dec. 1997
 ↑ Key Encapsulation: A New Scheme for PublicKey Encryption, XML Security Working Group F2F, May 2009
 ↑ http://www.dimgt.com.au/rsa_alg.html#weaknesses
 ↑ 518bit GNFS with msieve
 ↑ Has the RSA algorithm been compromised as a result of Bernstein's Paper? What key size should I be using?
 ↑ Template:Cite journal
 ↑ http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.80.1438&rep=rep1&type=pdf
 ↑ FaultBased Attack of RSA Authentication
References[]
 Template:Cite book
 Template:Cite book
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, Template:US patent.
 PKCS #1: RSA Cryptography Standard (RSA Laboratories website)
 The PKCS #1 standard "provides recommendations for the implementation of publickey 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".
 Thorough walk through of RSA
 Prime Number HideAndSeek: How the RSA Cipher Works
 Menezes, Oorschot, Vanstone, Scott: Handbook of Applied Cryptography (free PDF downloads), see Chapter 8
 Onur Aciicmez, Cetin Kaya Koc, JeanPierre 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
 Online RSA encryption application Template:Nl icon
 An animated explanation of RSA with its mathematical background by CrypTool

ar:خوارزمية آر إس إيه bg:RSA ca:RSA cs:RSA da:RSA de:RSAKryptosystem et:RSA (algoritm) el:RSA es:RSA eo:RSA eu:RSA fa:آراسای fr:Rivest Shamir Adleman gl:RSA ko:RSA 암호 hr:RSA id:RSA is:RSA it:RSA he:RSA ka:RSA ალგორითმი lv:RSA šifrēšanas algoritms lt:RSA hu:RSAeljárás nl:RSA (cryptografie) ja:RSA暗号 no:RSA pl:RSA (kryptografia) pt:RSA ro:RSA ru:RSA simple:RSA sl:RSA sr:RSA fi:RSA sv:RSA th:RSA tr:RSA uk:RSA vi:RSA (mã hóa) zh:RSA加密演算法