Public-key cryptography

<h2 id="description">Description</h2>
Before the mid-1970s, all cipher systems used <a href="/facts/Symmetric_key_algorithm/5zfe0b76">symmetric key algorithms</a>, in which the same <a href="/facts/Cryptographic_key/5W5PAmT4">cryptographic key</a> is used with the underlying algorithm by both the sender and the recipient, who must both keep it secret. Of necessity, the key in every such system had to be exchanged between the communicating parties in some secure way prior to any use of the system – for instance, via a <a href="/facts/Secure_channel/cWucANvf">secure channel</a>. This requirement is never trivial and very rapidly becomes unmanageable as the number of participants increases, or when secure channels are not available, or when, (as is sensible cryptographic practice), keys are frequently changed. In particular, if messages are meant to be secure from other users, a separate key is required for each possible pair of users.
By contrast, in a public-key cryptosystem, the public keys can be disseminated widely and openly, and only the corresponding private keys need be kept secret.
The two best-known types of public key cryptography are <a href="/facts/Digital_signature/tY7e2pnW">digital signature</a> and public-key encryption:

<ul><li>In a <a href="/facts/Digital_signature/tY7e2pnW">digital signature</a> system, a sender can use a private key together with a message to create a signature. Anyone with the corresponding public key can verify whether the signature matches the message, but a forger who does not know the private key cannot find any message/signature pair that will pass verification with the public key.<a class="footnote-ref" id="fnref:5" href="#fn:5">5</a><a class="footnote-ref" id="fnref:6" href="#fn:6">6</a><a class="footnote-ref" id="fnref:7" href="#fn:7">7</a>For example, a software publisher can create a signature key pair and include the public key in software installed on computers. Later, the publisher can distribute an update to the software signed using the private key, and any computer receiving an update can confirm it is genuine by verifying the signature using the public key. As long as the software publisher keeps the private key secret, even if a forger can distribute malicious updates to computers, they cannot convince the computers that any malicious updates are genuine.</li>
<li>In a public-key encryption system, anyone with a public key can encrypt a message, yielding a ciphertext, but only those who know the corresponding private key can decrypt the ciphertext to obtain the original message.<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a>For example, a journalist can publish the public key of an encryption key pair on a web site so that sources can send secret messages to the news organization in ciphertext.Only the journalist who knows the corresponding private key can decrypt the ciphertexts to obtain the sources' messages—an eavesdropper reading email on its way to the journalist cannot decrypt the ciphertexts. However, public-key encryption does not conceal <a href="/facts/Metadata/qt35z79C">metadata</a> like what computer a source used to send a message, when they sent it, or how long it is.<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a><a class="footnote-ref" id="fnref:10" href="#fn:10">10</a><a class="footnote-ref" id="fnref:11" href="#fn:11">11</a><a class="footnote-ref" id="fnref:12" href="#fn:12">12</a> Public-key encryption on its own also does not tell the recipient anything about who sent a message<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a>: 283 <a class="footnote-ref" id="fnref:14" href="#fn:14">14</a><a class="footnote-ref" id="fnref:15" href="#fn:15">15</a>—it just conceals the content of the message.</li></ul>
One important issue is confidence/proof that a particular public key is authentic, i.e. that it is correct and belongs to the person or entity claimed, and has not been tampered with or replaced by some (perhaps malicious) third party. There are several possible approaches, including:
A <a href="/facts/Public_key_infrastructure/7fwMLxF4">public key infrastructure</a> (PKI), in which one or more third parties – known as <a href="/facts/Certificate_authorities/WAo8vMTN">certificate authorities</a> – certify ownership of key pairs. <a href="/facts/Transport_Layer_Security/pGy16TnA">TLS</a> relies upon this. This implies that the PKI system (software, hardware, and management) is trust-able by all involved.
A "<a href="/facts/Web_of_trust/H2cy9v6s">web of trust</a>" decentralizes authentication by using individual endorsements of links between a user and the public key belonging to that user. <a href="/facts/Pretty_Good_Privacy/4BELG9BW">PGP</a> uses this approach, in addition to lookup in the <a href="/facts/Domain_name_system/rfxdWFsj">domain name system</a> (DNS). The <a href="/facts/DKIM/STA0jA68">DKIM</a> system for digitally signing emails also uses this approach.

<h2 id="applications">Applications</h2>
The most obvious application of a public key encryption system is for encrypting communication to provide <a href="/facts/Confidentiality/JFMubsQm">confidentiality</a> – a message that a sender encrypts using the recipient's public key, which can be decrypted only by the recipient's paired private key.
Another application in public key cryptography is the <a href="/facts/Digital_signature/tY7e2pnW">digital signature</a>. Digital signature schemes can be used for sender <a href="/facts/Authentication/64y4S69b">authentication</a>.
<a href="/facts/Non-repudiation/uNAP1YIf">Non-repudiation</a> systems use digital signatures to ensure that one party cannot successfully dispute its authorship of a document or communication.
Further applications built on this foundation include: <a href="/facts/Digital_cash/ycholMaA">digital cash</a>, <a href="/facts/Password-authenticated_key_agreement/udf3tV4x">password-authenticated key agreement</a>, <a href="/facts/Trusted_timestamping/eRjuYGTM">time-stamping services</a> and non-repudiation protocols.

<h2 id="hybrid-cryptosystems">Hybrid cryptosystems</h2>
Because asymmetric key algorithms are nearly always much more computationally intensive than symmetric ones, it is common to use a public/private asymmetric <a href="/facts/Key-exchange_algorithm/gcYhnpFb">key-exchange algorithm</a> to encrypt and exchange a symmetric key, which is then used by <a href="/facts/Symmetric-key_cryptography/5zfe0b76">symmetric-key cryptography</a> to transmit data using the now-shared symmetric key for a symmetric key encryption algorithm. <a href="/facts/Pretty_Good_Privacy/4BELG9BW">PGP</a>, <a href="/facts/SSH/wjVRw5zv">SSH</a>, and the <a href="/facts/SSL%2fTLS/pGy16TnA">SSL/TLS</a> family of schemes use this procedure; they are thus called <a href="/facts/Hybrid_cryptosystem/jR65zu0B">hybrid cryptosystems</a>. The initial asymmetric cryptography-based key exchange to share a server-generated symmetric key from the server to client has the advantage of not requiring that a symmetric key be pre-shared manually, such as on printed paper or discs transported by a courier, while providing the higher data throughput of symmetric key cryptography over asymmetric key cryptography for the remainder of the shared connection.

<h2 id="weaknesses">Weaknesses</h2>
As with all security-related systems, there are various potential weaknesses in public-key cryptography. Aside from poor choice of an asymmetric key algorithm (there are few that are widely regarded as satisfactory) or too short a key length, the chief security risk is that the private key of a pair becomes known. All security of messages, authentication, etc., will then be lost.
Additionally, with the advent of <a href="/facts/Quantum_computing/nbbcgmvq">quantum computing</a>, many asymmetric key algorithms are considered vulnerable to attacks, and new quantum-resistant schemes are being developed to overcome the problem.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a><a class="footnote-ref" id="fnref:17" href="#fn:17">17</a>

<h3>Algorithms</h3>
All public key schemes are in theory susceptible to a "<a href="/facts/Brute-force_attack/TXl8pkfb">brute-force key search attack</a>".<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a> However, such an attack is impractical if the amount of computation needed to succeed – termed the "work factor" by <a href="/facts/Claude_Shannon/EremsCws">Claude Shannon</a> – is out of reach of all potential attackers. In many cases, the work factor can be increased by simply choosing a longer key. But other algorithms may inherently have much lower work factors, making resistance to a brute-force attack (e.g., from longer keys) irrelevant. Some special and specific algorithms have been developed to aid in attacking some public key encryption algorithms; both <a href="/facts/RSA_(algorithm)/XTzyfHuq">RSA</a> and <a href="/facts/ElGamal_encryption/sKDVyMyR">ElGamal encryption</a> have known attacks that are much faster than the brute-force approach. None of these are sufficiently improved to be actually practical, however.
Major weaknesses have been found for several formerly promising asymmetric key algorithms. The <a href="/facts/Merkle%25E2%2580%2593Hellman_knapsack_cryptosystem/gWwGnLn5">"knapsack packing" algorithm</a> was found to be insecure after the development of a new attack.<a class="footnote-ref" id="fnref:19" href="#fn:19">19</a> As with all cryptographic functions, public-key implementations may be vulnerable to <a href="/facts/Side-channel_attack/2B1dfBty">side-channel attacks</a> that exploit information leakage to simplify the search for a secret key. These are often independent of the algorithm being used. Research is underway to both discover, and to protect against, new attacks.

<h3>Alteration of public keys</h3>
Another potential security vulnerability in using asymmetric keys is the possibility of a <a href="/facts/Man-in-the-middle_attack/dx4cojdz">"man-in-the-middle" attack</a>, in which the communication of public keys is intercepted by a third party (the "man in the middle") and then modified to provide different public keys instead. Encrypted messages and responses must, in all instances, be intercepted, decrypted, and re-encrypted by the attacker using the correct public keys for the different communication segments so as to avoid suspicion.
A communication is said to be insecure where data is transmitted in a manner that allows for interception (also called "<a href="/facts/Sniffing_attack/YKE35ED9">sniffing</a>"). These terms refer to reading the sender's private data in its entirety. A communication is particularly unsafe when interceptions can not be prevented or monitored by the sender.<a class="footnote-ref" id="fnref:20" href="#fn:20">20</a>
A man-in-the-middle attack can be difficult to implement due to the complexities of modern security protocols. However, the task becomes simpler when a sender is using insecure media such as public networks, the <a href="/facts/Internet/Xw1rVvJU">Internet</a>, or wireless communication. In these cases an attacker can compromise the communications infrastructure rather than the data itself. A hypothetical malicious staff member at an <a href="/facts/Internet_service_provider/dUacAxef">Internet service provider</a> (ISP) might find a man-in-the-middle attack relatively straightforward. Capturing the public key would only require searching for the key as it gets sent through the ISP's communications hardware; in properly implemented asymmetric key schemes, this is not a significant risk.
In some advanced man-in-the-middle attacks, one side of the communication will see the original data while the other will receive a malicious variant. Asymmetric man-in-the-middle attacks can prevent users from realizing their connection is compromised. This remains so even when one user's data is known to be compromised because the data appears fine to the other user. This can lead to confusing disagreements between users such as "it must be on your end!" when neither user is at fault. Hence, man-in-the-middle attacks are only fully preventable when the communications infrastructure is physically controlled by one or both parties; such as via a wired route inside the sender's own building. In summation, public keys are easier to alter when the communications hardware used by a sender is controlled by an attacker.<a class="footnote-ref" id="fnref:21" href="#fn:21">21</a><a class="footnote-ref" id="fnref:22" href="#fn:22">22</a><a class="footnote-ref" id="fnref:23" href="#fn:23">23</a>

<h3>Public key infrastructure</h3>
One approach to prevent such attacks involves the use of a <a href="/facts/Public_key_infrastructure/7fwMLxF4">public key infrastructure</a> (PKI); a set of roles, policies, and procedures needed to create, manage, distribute, use, store and <a href="/facts/Certificate_revocation/JSP12aR0">revoke</a> digital certificates and manage public-key encryption. However, this has potential weaknesses.
For example, the certificate authority issuing the certificate must be trusted by all participating parties to have properly checked the identity of the key-holder, to have ensured the correctness of the public key when it issues a certificate, to be secure from computer piracy, and to have made arrangements with all participants to check all their certificates before protected communications can begin. <a href="/facts/Web_browser/2pfyymLs">Web browsers</a>, for instance, are supplied with a long list of "self-signed identity certificates" from PKI providers – these are used to check the bona fides of the certificate authority and then, in a second step, the certificates of potential communicators. An attacker who could subvert one of those certificate authorities into issuing a certificate for a bogus public key could then mount a "man-in-the-middle" attack as easily as if the certificate scheme were not used at all. An attacker who penetrates an authority's servers and obtains its store of certificates and keys (public and private) would be able to spoof, masquerade, decrypt, and forge transactions without limit, assuming that they were able to place themselves in the communication stream.
Despite its theoretical and potential problems, Public key infrastructure is widely used. Examples include <a href="/facts/Transport_Layer_Security/pGy16TnA">TLS</a> and its predecessor <a href="/facts/Transport_Layer_Security/pGy16TnA">SSL</a>, which are commonly used to provide security for web browser transactions (for example, most websites utilize TLS for <a href="/facts/HTTPS/MSWYz4zo">HTTPS</a>).
Aside from the resistance to attack of a particular key pair, the security of the certification <a href="/facts/Hierarchy/mYJyqFrG">hierarchy</a> must be considered when deploying public key systems. Some certificate authority – usually a purpose-built program running on a server computer – vouches for the identities assigned to specific private keys by producing a digital certificate. <a href="/facts/Digital_certificate/J7aYI4Bx">Public key digital certificates</a> are typically valid for several years at a time, so the associated private keys must be held securely over that time. When a private key used for certificate creation higher in the PKI server hierarchy is compromised, or accidentally disclosed, then a "<a href="/facts/Man-in-the-middle_attack/dx4cojdz">man-in-the-middle attack</a>" is possible, making any subordinate certificate wholly insecure.

<h3>Unencrypted metadata</h3>
Most of the available public-key encryption software does not conceal <a href="/facts/Metadata/qt35z79C">metadata</a> in the message header, which might include the identities of the sender and recipient, the sending date, subject field, and the software they use etc. Rather, only the body of the message is concealed and can only be decrypted with the private key of the intended recipient. This means that a third party could construct quite a detailed model of participants in a communication network, along with the subjects being discussed, even if the message body itself is hidden.
However, there has been a recent demonstration of messaging with encrypted headers, which obscures the identities of the sender and recipient, and significantly reduces the available metadata to a third party.<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a> The concept is based around an open repository containing separately encrypted metadata blocks and encrypted messages. Only the intended recipient is able to decrypt the metadata block, and having done so they can identify and download their messages and decrypt them. Such a messaging system is at present in an experimental phase and not yet deployed. Scaling this method would reveal to the third party only the inbox server being used by the recipient and the timestamp of sending and receiving. The server could be shared by thousands of users, making social network modelling much more challenging.

<h2 id="history">History</h2>
During the early <a href="/facts/History_of_cryptography/7wvlxQrp">history of cryptography</a>, two parties would rely upon a key that they would exchange by means of a secure, but non-cryptographic, method such as a face-to-face meeting, or a trusted courier. This key, which both parties must then keep absolutely secret, could then be used to exchange encrypted messages. A number of significant practical difficulties arise with this approach to <a href="/facts/Key_distribution/6bUxRdbX">distributing keys</a>.

<h3>Anticipation</h3>
In his 1874 book The Principles of Science, <a href="/facts/William_Stanley_Jevons/guTGxIYP">William Stanley Jevons</a> wrote:<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a><blockquote>
Can the reader say what two numbers multiplied together will produce the number <a href="/facts/William_Stanley_Jevons/guTGxIYP">8616460799</a>?<a class="footnote-ref" id="fnref:26" href="#fn:26">26</a> I think it unlikely that anyone but myself will ever know.<a class="footnote-ref" id="fnref:27" href="#fn:27">27</a></blockquote>
Here he described the relationship of <a href="/facts/One-way_function/rGtcumDW">one-way functions</a> to cryptography, and went on to discuss specifically the <a href="/facts/Factorization/tXrBXFh1">factorization</a> problem used to create a <a href="/facts/Trapdoor_function/xMTTRrhY">trapdoor function</a>. In July 1996, mathematician <a href="/facts/Solomon_W._Golomb/dK5oajJ4">Solomon W. Golomb</a> said: "Jevons anticipated a key feature of the RSA Algorithm for public key cryptography, although he certainly did not invent the concept of public key cryptography."<a class="footnote-ref" id="fnref:28" href="#fn:28">28</a>

<h3>Classified discovery</h3>
In 1970, <a href="/facts/James_H._Ellis/fSgsv4h4">James H. Ellis</a>, a British cryptographer at the UK <a href="/facts/Government_Communications_Headquarters/XCMkfqWE">Government Communications Headquarters</a> (GCHQ), conceived of the possibility of "non-secret encryption", (now called public key cryptography), but could see no way to implement it.<a class="footnote-ref" id="fnref:29" href="#fn:29">29</a><a class="footnote-ref" id="fnref:30" href="#fn:30">30</a> 
In 1973, his colleague <a href="/facts/Clifford_Cocks/fFzNfqnL">Clifford Cocks</a> implemented what has become known as the <a href="/facts/RSA_(cryptosystem)/XTzyfHuq">RSA encryption algorithm</a>, giving a practical method of "non-secret encryption", and in 1974 another GCHQ mathematician and cryptographer, <a href="/facts/Malcolm_J._Williamson/TmMXKs5f">Malcolm J. Williamson</a>, developed what is now known as <a href="/facts/Diffie%25E2%2580%2593Hellman_key_exchange/xR4YQcaD">Diffie–Hellman key exchange</a>. 
The scheme was also passed to the US's <a href="/facts/National_Security_Agency/Sg6MGV1o">National Security Agency</a>.<a class="footnote-ref" id="fnref:31" href="#fn:31">31</a> Both organisations had a military focus and only limited computing power was available in any case; the potential of public key cryptography remained unrealised by either organization:

<blockquote>
I judged it most important for military use ... if you can share your key rapidly and electronically, you have a major advantage over your opponent. Only at the end of the evolution from <a href="/facts/Tim_Berners-Lee/JRv21mt9">Berners-Lee</a> designing an open internet architecture for <a href="/facts/CERN/y1gwRchm">CERN</a>, its adaptation and adoption for the <a href="/facts/Arpanet/LyMGWurJ">Arpanet</a> ... did public key cryptography realise its full potential.
—<a href="/facts/Ralph_Benjamin/kNafA0sL">Ralph Benjamin</a><a class="footnote-ref" id="fnref:32" href="#fn:32">32</a>

</blockquote>
These discoveries were not publicly acknowledged for 27 years, until the research was declassified by the British government in 1997.<a class="footnote-ref" id="fnref:33" href="#fn:33">33</a>

<h3>Public discovery</h3>
In 1976, an asymmetric key cryptosystem was published by <a href="/facts/Whitfield_Diffie/oDKz7ChA">Whitfield Diffie</a> and <a href="/facts/Martin_Hellman/QCxKCFgn">Martin Hellman</a> who, influenced by <a href="/facts/Ralph_Merkle/ua5bsN0I">Ralph Merkle</a>'s work on public key distribution, disclosed a method of public key agreement. This method of key exchange, which uses <a href="/facts/Finite_field/UkMGJo3m">exponentiation in a finite field</a>, came to be known as <a href="/facts/Diffie%25E2%2580%2593Hellman_key_exchange/xR4YQcaD">Diffie–Hellman key exchange</a>.<a class="footnote-ref" id="fnref:34" href="#fn:34">34</a> This was the first published practical method for establishing a shared secret-key over an authenticated (but not confidential) communications channel without using a prior shared secret. Merkle's "public key-agreement technique" became known as <a href="/facts/Merkle%2527s_Puzzles/V8SSJ1JF">Merkle's Puzzles</a>, and was invented in 1974 and only published in 1978. This makes asymmetric encryption a rather new field in cryptography although cryptography itself dates back more than 2,000 years.<a class="footnote-ref" id="fnref:35" href="#fn:35">35</a>
In 1977, a generalization of Cocks's scheme was independently invented by <a href="/facts/Ron_Rivest/nQsIcAKa">Ron Rivest</a>, <a href="/facts/Adi_Shamir/CTnaUeP6">Adi Shamir</a> and <a href="/facts/Leonard_Adleman/uSGnztdj">Leonard Adleman</a>, all then at <a href="/facts/MIT/Xk49vNA8">MIT</a>. The latter authors published their work in 1978 in <a href="/facts/Martin_Gardner/HGfEnPDH">Martin Gardner</a>'s <a href="/facts/Scientific_American/jkl8bhUN">Scientific American</a> column, and the algorithm came to be known as <a href="/facts/RSA_(cryptosystem)/XTzyfHuq">RSA</a>, from their initials.<a class="footnote-ref" id="fnref:36" href="#fn:36">36</a> RSA uses <a href="/facts/Modular_exponentiation/0STECS3P">exponentiation modulo</a> a product of two very large <a href="/facts/Prime/L20FLkgn">primes</a>, to encrypt and decrypt, performing both public key encryption and public key digital signatures. Its security is connected to the extreme difficulty of <a href="/facts/Integer_factorization/EjMCTz2t">factoring large integers</a>, a problem for which there is no known efficient general technique. A description of the algorithm was published in the <a href="/facts/List_of_Martin_Gardner_Mathematical_Games_columns/t6N9eshI">Mathematical Games</a> column in the August 1977 issue of <a href="/facts/Scientific_American/jkl8bhUN">Scientific American</a>.<a class="footnote-ref" id="fnref:37" href="#fn:37">37</a>
Since the 1970s, a large number and variety of encryption, digital signature, key agreement, and other techniques have been developed, including the <a href="/facts/Rabin_cryptosystem/Q7MRkmdo">Rabin cryptosystem</a>, <a href="/facts/ElGamal_encryption/sKDVyMyR">ElGamal encryption</a>, <a href="/facts/Digital_Signature_Algorithm/0o0FK486">DSA</a> and <a href="/facts/Elliptic-curve_cryptography/YbjcXIWk">ECC</a>.

<h2 id="examples">Examples</h2>
Examples of well-regarded asymmetric key techniques for varied purposes include:

<ul><li><a href="/facts/Diffie%25E2%2580%2593Hellman_key_exchange/xR4YQcaD">Diffie–Hellman key exchange</a> protocol</li>
<li>DSS (Digital Signature Standard), which incorporates the <a href="/facts/Digital_Signature_Algorithm/0o0FK486">Digital Signature Algorithm</a></li>
<li><a href="/facts/ElGamal/sKDVyMyR">ElGamal</a></li>
<li><a href="/facts/Elliptic-curve_cryptography/YbjcXIWk">Elliptic-curve cryptography</a>
<ul><li><a href="/facts/Elliptic_Curve_Digital_Signature_Algorithm/gl0mfnS1">Elliptic Curve Digital Signature Algorithm</a> (ECDSA)</li>
<li><a href="/facts/Elliptic-curve_Diffie%25E2%2580%2593Hellman/zy3IJCeK">Elliptic-curve Diffie–Hellman</a> (ECDH)</li>
<li><a href="/facts/Ed25519/IbTRBhK3">Ed25519</a> and <a href="/facts/Ed448/IbTRBhK3">Ed448</a> (<a href="/facts/EdDSA/IbTRBhK3">EdDSA</a>)</li>
<li><a href="/facts/X25519/wLr6FMkV">X25519</a> and <a href="/facts/X448/gsN24bb9">X448</a> (ECDH/EdDH)</li></ul></li>
<li>Various <a href="/facts/Password-authenticated_key_agreement/udf3tV4x">password-authenticated key agreement</a> techniques</li>
<li><a href="/facts/Paillier_cryptosystem/oLl6TR8H">Paillier cryptosystem</a></li>
<li><a href="/facts/RSA_(cryptosystem)/XTzyfHuq">RSA</a> encryption algorithm (<a href="/facts/PKCS1/I6JD53RG">PKCS#1</a>)</li>
<li><a href="/facts/Cramer%25E2%2580%2593Shoup_cryptosystem/H3D1mceX">Cramer–Shoup cryptosystem</a></li>
<li><a href="/facts/YAK_(cryptography)/cLTKAArX">YAK</a> authenticated key agreement protocol</li></ul>
Examples of asymmetric key algorithms not yet widely adopted include:

<ul><li><a href="/facts/NTRUEncrypt/B6MR5HkI">NTRUEncrypt</a> cryptosystem</li>
<li><a href="/facts/Kyber/FgSGHwCx">Kyber</a></li>
<li><a href="/facts/McEliece_cryptosystem/Yb3X3nzs">McEliece cryptosystem</a></li></ul>
Examples of notable – yet insecure – asymmetric key algorithms include:

<ul><li><a href="/facts/Merkle%25E2%2580%2593Hellman_knapsack_cryptosystem/gWwGnLn5">Merkle–Hellman knapsack cryptosystem</a></li></ul>
Examples of protocols using asymmetric key algorithms include:

<ul><li><a href="/facts/S%2fMIME/YufdsBt3">S/MIME</a></li>
<li><a href="/facts/GNU_Privacy_Guard/EqmGmx7V">GPG</a>, an implementation of <a href="/facts/OpenPGP/4BELG9BW">OpenPGP</a>, and an Internet Standard</li>
<li><a href="/facts/EMV/XRpvtwYw">EMV</a>, EMV Certificate Authority</li>
<li><a href="/facts/IPsec/01MwcET1">IPsec</a></li>
<li><a href="/facts/Pretty_Good_Privacy/4BELG9BW">PGP</a></li>
<li><a href="/facts/ZRTP/QLW7PIwP">ZRTP</a>, a secure <a href="/facts/VoIP/5QGBbXYg">VoIP</a> protocol</li>
<li><a href="/facts/Transport_Layer_Security/pGy16TnA">Transport Layer Security</a> standardized by <a href="/facts/IETF/tIcCsFhX">IETF</a> and its predecessor <a href="/facts/Secure_Socket_Layer/pGy16TnA">Secure Socket Layer</a></li>
<li><a href="/facts/SILC_(protocol)/7fMtW1ND">SILC</a></li>
<li><a href="/facts/SSH/wjVRw5zv">SSH</a></li>
<li><a href="/facts/Bitcoin/UJvqfray">Bitcoin</a></li>
<li><a href="/facts/Off-the-Record_Messaging/RMdcs0f4">Off-the-Record Messaging</a></li></ul>
<h2 id="see-also">See also</h2>

<ul><li><a href="/facts/Books_on_cryptography/xy8TKgPr">Books on cryptography</a></li>
<li><a href="/facts/GNU_Privacy_Guard/EqmGmx7V">GNU Privacy Guard</a></li>
<li><a href="/facts/Identity-based_encryption/xgYEomQ9">Identity-based encryption</a> (IBE)</li>
<li><a href="/facts/Key_escrow/vfE3jPkC">Key escrow</a></li>
<li><a href="/facts/Key-agreement_protocol/W1DErngS">Key-agreement protocol</a></li>
<li><a href="/facts/PGP_word_list/Dl822FFv">PGP word list</a></li>
<li><a href="/facts/Post-quantum_cryptography/1qeqUQve">Post-quantum cryptography</a></li>
<li><a href="/facts/Pretty_Good_Privacy/4BELG9BW">Pretty Good Privacy</a></li>
<li><a href="/facts/Pseudonym/A5EjmWxQ">Pseudonym</a></li>
<li><a href="/facts/Public_key_fingerprint/tne3mX6r">Public key fingerprint</a></li>
<li><a href="/facts/Public_key_infrastructure/7fwMLxF4">Public key infrastructure</a> (PKI)</li>
<li><a href="/facts/Quantum_computing/nbbcgmvq">Quantum computing</a></li>
<li><a href="/facts/Quantum_cryptography/FPqPdNXT">Quantum cryptography</a></li>
<li><a href="/facts/Secure_Shell/wjVRw5zv">Secure Shell</a> (SSH)</li>
<li><a href="/facts/Symmetric-key_algorithm/5zfe0b76">Symmetric-key algorithm</a></li>
<li><a href="/facts/Threshold_cryptosystem/4KKvNxW8">Threshold cryptosystem</a></li>
<li><a href="/facts/Web_of_trust/H2cy9v6s">Web of trust</a></li></ul>

<h2 id="notes">Notes</h2>

<ul><li>Hirsch, Frederick J. <a href="https://httpd.apache.org/docs/2.2/ssl/ssl_intro.html#cryptographictech">"SSL/TLS Strong Encryption: An Introduction"</a>. Apache HTTP Server. Retrieved 17 April 2013.. The first two sections contain a very good introduction to public-key cryptography.</li>
<li><a href="/facts/Niels_Ferguson/hCX1IMQb">Ferguson, Niels</a>; <a href="/facts/Bruce_Schneier/kWxPFPmQ">Schneier, Bruce</a> (2003). Practical Cryptography. <a href="/facts/John_Wiley_%2526_Sons/53g3LqJc">Wiley</a>. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-471-22357-3.</li>
<li><a href="/facts/Jon_Katz/HJGdV3KS">Katz, Jon</a>; Lindell, Y. (2007). <a href="https://archive.org/details/Introduction_to_Modern_Cryptography">Introduction to Modern Cryptography</a>. <a href="/facts/CRC_Press/duTuH4hz">CRC Press</a>. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 978-1-58488-551-1.</li>
<li><a href="/facts/Alfred_Menezes/nduu6dew">Menezes, A. J.</a>; van Oorschot, P. C.; <a href="/facts/Scott_Vanstone/KcQlUQAY">Vanstone, Scott A.</a> (1997). <a href="https://archive.org/details/handbookofapplie0000mene">Handbook of Applied Cryptography</a>. Taylor & Francis. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-8493-8523-7.</li>
<li><a href="https://web.archive.org/web/20081119061833/http://grouper.ieee.org/groups/1363/">IEEE 1363: Standard Specifications for Public-Key Cryptography</a></li>
<li>Christof Paar, Jan Pelzl, <a href="https://archive.today/20121208212741/http://wiki.crypto.rub.de/Buch/movies.php">"Introduction to Public-Key Cryptography"</a>, Chapter 6 of "Understanding Cryptography, A Textbook for Students and Practitioners". (companion web site contains online cryptography course that covers public-key cryptography), Springer, 2009.</li>
<li>Salomaa, Arto (1996). Public-Key Cryptography (2 ed.). Berlin: <a href="/facts/Springer_Science%252BBusiness_Media/nAesf6nT">Springer</a>. 275. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1007%2F978-3-662-03269-5">10.1007/978-3-662-03269-5</a>. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 978-3-662-03269-5. <a href="/facts/S2CID_(identifier)/ldJsHa2Y">S2CID</a> <a href="https://api.semanticscholar.org/CorpusID:24751345">24751345</a>.</li></ul>
<h2 id="external-links">External links</h2>
<ul><li><a href="http://conservancy.umn.edu/handle/11299/107353">Oral history interview with Martin Hellman</a>, <a href="/facts/Charles_Babbage_Institute/7CbplQuX">Charles Babbage Institute</a>, University of Minnesota. Leading cryptography scholar <a href="/facts/Martin_Hellman/QCxKCFgn">Martin Hellman</a> discusses the circumstances and fundamental insights of his invention of public key cryptography with collaborators <a href="/facts/Whitfield_Diffie/oDKz7ChA">Whitfield Diffie</a> and <a href="/facts/Ralph_Merkle/ua5bsN0I">Ralph Merkle</a> at Stanford University in the mid-1970s.</li>
<li><a href="https://web.archive.org/web/20080625052129/http://www.ladlass.com/intel/archives/010256.html">An account of how GCHQ kept their invention of PKE secret until 1997</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">R. Shirey (August 2007). Internet Security Glossary, Version 2. Network Working Group. doi:10.17487/RFC4949. RFC 4949. Informational.
 <a href="https://datatracker.ietf.org/doc/html/rfc4949" target="_blank">https://datatracker.ietf.org/doc/html/rfc4949</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Bernstein, Daniel J.; Lange, Tanja (14 September 2017). "Post-quantum cryptography". Nature. 549 (7671): 188–194. Bibcode:2017Natur.549..188B. doi:10.1038/nature23461. ISSN 0028-0836. PMID 28905891. S2CID 4446249. <a href="http://www.nature.com/articles/nature23461" target="_blank">http://www.nature.com/articles/nature23461</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">Stallings, William (3 May 1990). Cryptography and Network Security: Principles and Practice. Prentice Hall. p. 165. ISBN 9780138690175. <a href="9780138690175" target="_blank">9780138690175</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">Alvarez, Rafael; Caballero-Gil, Cándido; Santonja, Juan; Zamora, Antonio (27 June 2017). "Algorithms for Lightweight Key Exchange". Sensors. 17 (7): 1517. doi:10.3390/s17071517. ISSN 1424-8220. PMC 5551094. PMID 28654006. <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5551094" target="_blank">https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5551094</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">Menezes, Alfred J.; van Oorschot, Paul C.; Vanstone, Scott A. (October 1996). "Chapter 8: Public-key encryption". Handbook of Applied Cryptography (PDF). CRC Press. pp. 425–488. ISBN 0-8493-8523-7. Retrieved 8 October 2022. <a href="0-8493-8523-7" target="_blank">0-8493-8523-7</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Bernstein, Daniel J. (1 May 2008). "Protecting communications against forgery". Algorithmic Number Theory (PDF). Vol. 44. MSRI Publications. §5: Public-key signatures, pp. 543–545. Retrieved 8 October 2022. <a href="/wiki/Daniel_J._Bernstein" target="_blank">/wiki/Daniel_J._Bernstein</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">Bellare, Mihir; Goldwasser, Shafi (July 2008). "Chapter 10: Digital signatures". Lecture Notes on Cryptography (PDF). p. 168. Archived (PDF) from the original on 20 April 2022. Retrieved 11 June 2023. <a href="/wiki/Mihir_Bellare" target="_blank">/wiki/Mihir_Bellare</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">Menezes, Alfred J.; van Oorschot, Paul C.; Vanstone, Scott A. (October 1996). "8: Public-key encryption". Handbook of Applied Cryptography (PDF). CRC Press. pp. 283–319. ISBN 0-8493-8523-7. Retrieved 8 October 2022. <a href="0-8493-8523-7" target="_blank">0-8493-8523-7</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">Danezis, George; Diaz, Claudia; Syverson, Paul (2010). "Chapter 13: Anonymous Communication". In Rosenberg, Burton (ed.). Handbook of Financial Cryptography and Security (PDF). Chapman & Hall/CRC. pp. 341–390. ISBN 978-1420059816. Since PGP, beyond compressing the messages, does not make any further attempts to hide their size, it is trivial to follow a message in the network just by observing its length. <a href="978-1420059816" target="_blank">978-1420059816</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">Rackoff, Charles; Simon, Daniel R. (1993). "Cryptographic defense against traffic analysis". Proceedings of the twenty-fifth annual ACM symposium on Theory of Computing. STOC '93: ACM Symposium on the Theory of Computing. Association for Computing Machinery. pp. 672–681. doi:10.1145/167088.167260. Now, certain types of information cannot reasonably be assumed to be concealed. For instance, an upper bound on the total volume of a party's sent or received communication (of any sort) is obtainable by anyone with the resources to examine all possible physical communication channels available to that party. <a href="/wiki/Charles_Rackoff" target="_blank">/wiki/Charles_Rackoff</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">Karger, Paul A. (May 1977). "11: Limitations of End-to-End Encryption". Non-Discretionary Access Control for Decentralized Computing Systems (S.M. thesis). Laboratory for Computer Science, Massachusetts Institute of Technology. hdl:1721.1/149471. The scenario just described would seem to be secure, because all data is encrypted before being passed to the communications processors. However, certain control information must be passed in cleartext from the host to the communications processor to allow the network to function. This control information consists of the destination address for the packet, the length of the packet, and the time between successive packet transmissions. <a href="https://dspace.mit.edu/handle/1721.1/149471" target="_blank">https://dspace.mit.edu/handle/1721.1/149471</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">Chaum, David L. (February 1981). Rivest, R. (ed.). "Untraceable Electronic Mail, Return Addresses, and Digital Pseudonyms". Communications of the ACM. 24 (2). Association for Computing Machinery. Recently, some new solutions to the "key distribution problem" (the problem of providing each communicant with a secret key) have been suggested, under the name of public key cryptography. Another cryptographic problem, the "traffic analysis problem" (the problem of keeping confidential who converses with whom, and when they converse), will become increasingly important with the growth of electronic mail. <a href="/wiki/David_Chaum" target="_blank">/wiki/David_Chaum</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">Menezes, Alfred J.; van Oorschot, Paul C.; Vanstone, Scott A. (October 1996). "8: Public-key encryption". Handbook of Applied Cryptography (PDF). CRC Press. pp. 283–319. ISBN 0-8493-8523-7. Retrieved 8 October 2022. <a href="0-8493-8523-7" target="_blank">0-8493-8523-7</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">Davis, Don (2001). "Defective Sign & Encrypt in S/MIME, PKCS#7, MOSS, PEM, PGP, and XML". Proceedings of the 2001 USENIX Annual Technical Conference. USENIX. pp. 65–78. Why is naïve Sign & Encrypt insecure? Most simply, S&E is vulnerable to "surreptitious forwarding:" Alice signs & encrypts for Bob's eyes, but Bob re-encrypts Alice's signed message for Charlie to see. In the end, Charlie believes Alice wrote to him directly, and can't detect Bob's subterfuge. <a href="https://www.usenix.org/legacy/events/usenix01/full_papers/davis/davis_html/" target="_blank">https://www.usenix.org/legacy/events/usenix01/full_papers/davis/davis_html/</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">An, Jee Hea (12 September 2001). Authenticated Encryption in the Public-Key Setting: Security Notions and Analyses (Technical report). IACR Cryptology ePrint Archive. 2001/079. Retrieved 24 November 2024. <a href="https://eprint.iacr.org/2001/079" target="_blank">https://eprint.iacr.org/2001/079</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">Escribano Pablos, José Ignacio; González Vasco, María Isabel (April 2023). "Secure post-quantum group key exchange: Implementing a solution based on Kyber". IET Communications. 17 (6): 758–773. doi:10.1049/cmu2.12561. hdl:10016/37141. ISSN 1751-8628. S2CID 255650398. <a href="https://ietresearch.onlinelibrary.wiley.com/doi/10.1049/cmu2.12561" target="_blank">https://ietresearch.onlinelibrary.wiley.com/doi/10.1049/cmu2.12561</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">Stohrer, Christian; Lugrin, Thomas (2023), Mulder, Valentin; Mermoud, Alain; Lenders, Vincent; Tellenbach, Bernhard (eds.), "Asymmetric Encryption", Trends in Data Protection and Encryption Technologies, Cham: Springer Nature Switzerland, pp. 11–14, doi:10.1007/978-3-031-33386-6_3, ISBN 978-3-031-33386-6 <a href="978-3-031-33386-6" target="_blank">978-3-031-33386-6</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">Paar, Christof; Pelzl, Jan; Preneel, Bart (2010). Understanding Cryptography: A Textbook for Students and Practitioners. Springer. ISBN 978-3-642-04100-6. <a href="978-3-642-04100-6" target="_blank">978-3-642-04100-6</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">Shamir, Adi (November 1982). "A polynomial time algorithm for breaking the basic Merkle-Hellman cryptosystem". 23rd Annual Symposium on Foundations of Computer Science (SFCS 1982): 145–152. doi:10.1109/SFCS.1982.5. <a href="https://ieeexplore.ieee.org/document/4568386" target="_blank">https://ieeexplore.ieee.org/document/4568386</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">Tunggal, Abi (20 February 2020). "What Is a Man-in-the-Middle Attack and How Can It Be Prevented – What is the difference between a man-in-the-middle attack and sniffing?". UpGuard. Retrieved 26 June 2020.[self-published source?] <a href="https://www.upguard.com/blog/man-in-the-middle-attack#mitm-sniffing" target="_blank">https://www.upguard.com/blog/man-in-the-middle-attack#mitm-sniffing</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">Tunggal, Abi (20 February 2020). "What Is a Man-in-the-Middle Attack and How Can It Be Prevented - Where do man-in-the-middle attacks happen?". UpGuard. Retrieved 26 June 2020.[self-published source?] <a href="https://www.upguard.com/blog/man-in-the-middle-attack#where" target="_blank">https://www.upguard.com/blog/man-in-the-middle-attack#where</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">martin (30 January 2013). "China, GitHub and the man-in-the-middle". GreatFire. Archived from the original on 19 August 2016. Retrieved 27 June 2015.[self-published source?] <a href="https://web.archive.org/web/20160819165216/https://en.greatfire.org/blog/2013/jan/china-github-and-man-middle" target="_blank">https://web.archive.org/web/20160819165216/https://en.greatfire.org/blog/2013/jan/china-github-and-man-middle</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">percy (4 September 2014). "Authorities launch man-in-the-middle attack on Google". GreatFire. Retrieved 26 June 2020.[self-published source?] <a href="https://en.greatfire.org/blog/2014/sep/authorities-launch-man-middle-attack-google" target="_blank">https://en.greatfire.org/blog/2014/sep/authorities-launch-man-middle-attack-google</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">Bjorgvinsdottir, Hanna; Bentley, Phil (24 June 2021). "Warp2: A Method of Email and Messaging with Encrypted Addressing and Headers". arXiv:1411.6409 [cs.CR]. <a href="/wiki/ArXiv_(identifier)" target="_blank">/wiki/ArXiv_(identifier)</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">Jevons, W.S. (1874). The Principles of Science: A Treatise on Logic and Scientific Method. Macmillan & Co. p. 141. Retrieved 18 January 2024. <a href="https://archive.org/details/principlesofscie00jevorich/principlesofscie00jevorich/page/n166/mode/1up?view=theater" target="_blank">https://archive.org/details/principlesofscie00jevorich/principlesofscie00jevorich/page/n166/mode/1up?view=theater</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">Weisstein, E.W. (2024). "Jevons' Number". MathWorld. Retrieved 18 January 2024. <a href="https://mathworld.wolfram.com/JevonsNumber.html" target="_blank">https://mathworld.wolfram.com/JevonsNumber.html</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">Jevons, W.S. (1874). The Principles of Science: A Treatise on Logic and Scientific Method. Macmillan & Co. p. 141. Retrieved 18 January 2024. <a href="https://archive.org/details/principlesofscie00jevorich/principlesofscie00jevorich/page/n166/mode/1up?view=theater" target="_blank">https://archive.org/details/principlesofscie00jevorich/principlesofscie00jevorich/page/n166/mode/1up?view=theater</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
<li id="fn:28">Golob, Solomon W. (1996). "On Factoring Jevons' Number". Cryptologia. 20 (3): 243. doi:10.1080/0161-119691884933. S2CID 205488749. <a href="/wiki/Doi_(identifier)" target="_blank">/wiki/Doi_(identifier)</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></li>
<li id="fn:29">Ellis, James H. (January 1970). "The Possibility of Secure Non-secret Digital Encryption" (PDF). CryptoCellar. Retrieved 18 January 2024. <a href="https://cryptocellar.org/cesg/possnse.pdf" target="_blank">https://cryptocellar.org/cesg/possnse.pdf</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></li>
<li id="fn:30">Sawer, Patrick (11 March 2016). "The unsung genius who secured Britain's computer defences and paved the way for safe online shopping". The Telegraph. <a href="https://www.newindianexpress.com/world/2016/mar/12/the-anonymous-researcher-who-held-the-key-to-cyber-security-910751.html" target="_blank">https://www.newindianexpress.com/world/2016/mar/12/the-anonymous-researcher-who-held-the-key-to-cyber-security-910751.html</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></li>
<li id="fn:31">Espiner, Tom (26 October 2010). "GCHQ pioneers on birth of public key crypto". ZDNet. <a href="https://www.zdnet.com/article/gchq-pioneers-on-birth-of-public-key-crypto/" target="_blank">https://www.zdnet.com/article/gchq-pioneers-on-birth-of-public-key-crypto/</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></li>
<li id="fn:32">Espiner, Tom (26 October 2010). "GCHQ pioneers on birth of public key crypto". ZDNet. <a href="https://www.zdnet.com/article/gchq-pioneers-on-birth-of-public-key-crypto/" target="_blank">https://www.zdnet.com/article/gchq-pioneers-on-birth-of-public-key-crypto/</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></li>
<li id="fn:33">Singh, Simon (1999). The Code Book. Doubleday. pp. 279–292. <a href="/wiki/Simon_Singh" target="_blank">/wiki/Simon_Singh</a> <a href="#fnref:33" class="footnote-back-ref">↩</a></li>
<li id="fn:34">Diffie, Whitfield; Hellman, Martin E. (November 1976). "New Directions in Cryptography" (PDF). IEEE Transactions on Information Theory. 22 (6): 644–654. CiteSeerX 10.1.1.37.9720. doi:10.1109/TIT.1976.1055638. Archived (PDF) from the original on 29 November 2014. <a href="/wiki/Whitfield_Diffie" target="_blank">/wiki/Whitfield_Diffie</a> <a href="#fnref:34" class="footnote-back-ref">↩</a></li>
<li id="fn:35">"Asymmetric encryption". IONOS Digitalguide. Retrieved 9 June 2022. <a href="https://www.ionos.com/digitalguide/server/security/public-key-encryption/" target="_blank">https://www.ionos.com/digitalguide/server/security/public-key-encryption/</a> <a href="#fnref:35" class="footnote-back-ref">↩</a></li>
<li id="fn:36">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. CiteSeerX 10.1.1.607.2677. doi:10.1145/359340.359342. S2CID 2873616. Archived from the original (PDF) on 17 December 2008. Retrieved 15 November 2019. <a href="https://web.archive.org/web/20081217101831/http://people.csail.mit.edu/rivest/Rsapaper.pdf" target="_blank">https://web.archive.org/web/20081217101831/http://people.csail.mit.edu/rivest/Rsapaper.pdf</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></li>
<li id="fn:37">Robinson, Sara (June 2003). "Still Guarding Secrets after Years of Attacks, RSA Earns Accolades for its Founders" (PDF). SIAM News. 36 (5). <a href="http://www.msri.org/people/members/sara/articles/rsa.pdf" target="_blank">http://www.msri.org/people/members/sara/articles/rsa.pdf</a> <a href="#fnref:37" class="footnote-back-ref">↩</a></li>
</ol>

Public-key cryptography open-in-new

Public-key cryptography