# Elliptic-curve **cryptography**

**Elliptic-curve cryptography** (

**ECC**) is an approach to public-key

**cryptography**based on the algebraic structure of elliptic curves over finite fields. ECC allows smaller keys compared to non-EC

**cryptography**(based on plain Galois fields) to provide equivalent security.

^{[1]}

Elliptic curves are applicable for key agreement, digital signatures, pseudo-random generators and other tasks. Indirectly, they can be used for encryption by combining the key agreement with a symmetric encryption scheme. They are also used in several integer factorization algorithms based on elliptic curves that have applications in **cryptography**, such as Lenstra elliptic-curve factorization.

## Rationale[edit]

Public-key **cryptography** is based on the intractability of certain mathematical problems. Early public-key systems based their security on the assumption that it is difficult to factor a large integer composed of two or more large prime factors. For later elliptic-curve-based protocols, the base assumption is that finding the discrete logarithm of a random elliptic curve element with respect to a publicly known base point is infeasible: this is the "elliptic curve discrete logarithm problem" (ECDLP). The security of elliptic curve **cryptography** depends on the ability to compute a point multiplication and the inability to compute the multiplicand given the original and product points. The size of the elliptic curve determines the difficulty of the problem.

The U.S. National Institute of Standards and Technology (NIST) has endorsed elliptic curve **cryptography** in its Suite B set of recommended algorithms, specifically elliptic-curve Diffie–Hellman (ECDH) for key exchange and Elliptic Curve Digital Signature Algorithm (ECDSA) for digital signature. The U.S. National Security Agency (NSA) allows their use for protecting information classified up to top secret with 384-bit keys.^{[2]} However, in August 2015, the NSA announced that it plans to replace Suite B with a new cipher suite due to concerns about quantum computing attacks on ECC.^{[3]}

While the RSA patent expired in 2000, there may be patents in force covering certain aspects of ECC technology. However some argue that the US government elliptic curve digital signature standard (ECDSA; NIST FIPS 186-3) and certain practical ECC-based key exchange schemes (including ECDH) can be implemented without infringing them, including RSA Laboratories^{[4]} and Daniel J. Bernstein.^{[5]}

The primary benefit promised by elliptic curve **cryptography** is a smaller key size, reducing storage and transmission requirements,^{[6]} i.e. that an elliptic curve group could provide the same level of security afforded by an RSA-based system with a large modulus and correspondingly larger key: for example, a 256-bit elliptic curve public key should provide comparable security to a 3072-bit RSA public key.

## History[edit]

The use of elliptic curves in **cryptography** was suggested independently by Neal Koblitz^{[7]} and Victor S. Miller^{[8]} in 1985. Elliptic curve **cryptography** algorithms entered wide use in 2004 to 2005.

## Theory[edit]

For current cryptographic purposes, an *elliptic curve* is a plane curve over a finite field (rather than the real numbers) which consists of the points satisfying the equation

along with a distinguished point at infinity, denoted ∞. (The coordinates here are to be chosen from a fixed finite field of characteristic not equal to 2 or 3, or the curve equation will be somewhat more complicated.)

This set together with the group operation of elliptic curves is an abelian group, with the point at infinity as an identity element. The structure of the group is inherited from the divisor group of the underlying algebraic variety.

## Cryptographic schemes[edit]

Several discrete logarithm-based protocols have been adapted to elliptic curves, replacing the group with an elliptic curve:

- The Elliptic Curve Diffie–Hellman (ECDH) key agreement scheme is based on the Diffie–Hellman scheme,
- The Elliptic Curve Integrated Encryption Scheme (ECIES), also known as Elliptic Curve Augmented Encryption Scheme or simply the Elliptic Curve Encryption Scheme,
- The Elliptic Curve Digital Signature Algorithm (ECDSA) is based on the Digital Signature Algorithm,
- The deformation scheme using Harrison's p-adic Manhattan metric,
- The Edwards-curve Digital Signature Algorithm (EdDSA) is based on Schnorr signature and uses twisted Edwards curves,
- The ECMQV key agreement scheme is based on the MQV key agreement scheme,
- The ECQV implicit certificate scheme.

At the RSA Conference 2005, the National Security Agency (NSA) announced Suite B which exclusively uses ECC for digital signature generation and key exchange. The suite is intended to protect both classified and unclassified national security systems and information.^{[6]}

Recently, a large number of cryptographic primitives based on bilinear mappings on various elliptic curve groups, such as the Weil and Tate pairings, have been introduced. Schemes based on these primitives provide efficient identity-based encryption as well as pairing-based signatures, signcryption, key agreement, and proxy re-encryption.

## Implementation[edit]

Some common implementation considerations include:

### Domain parameters[edit]

To use ECC, all parties must agree on all the elements defining the elliptic curve, that is, the *domain parameters* of the scheme. The field is defined by *p* in the prime case and the pair of *m* and *f* in the binary case. The elliptic curve is defined by the constants *a* and *b* used in its defining equation. Finally, the cyclic subgroup is defined by its *generator* (a.k.a. *base point*) *G*. For cryptographic application the order of *G*, that is the smallest positive number *n* such that (the point at infinity of the curve, and the identity element), is normally prime. Since *n* is the size of a subgroup of it follows from Lagrange's theorem that the number is an integer. In cryptographic applications this number *h*, called the *cofactor*, must be small () and, preferably, . To summarize: in the prime case, the domain parameters are ; in the binary case, they are .

Unless there is an assurance that domain parameters were generated by a party trusted with respect to their use, the domain parameters *must* be validated before use.

The generation of domain parameters is not usually done by each participant because this involves computing the number of points on a curve which is time-consuming and troublesome to implement. As a result, several standard bodies published domain parameters of elliptic curves for several common field sizes. Such domain parameters are commonly known as "standard curves" or "named curves"; a named curve can be referenced either by name or by the unique object identifier defined in the standard documents:

- NIST, Recommended Elliptic Curves for Government Use
- SECG, SEC 2: Recommended Elliptic Curve Domain Parameters
- ECC Brainpool (RFC 5639), ECC Brainpool Standard Curves and Curve Generation

SECG test vectors are also available.^{[9]} NIST has approved many SECG curves, so there is a significant overlap between the specifications published by NIST and SECG. EC domain parameters may be either specified by value or by name.

If one (despite the above) wants to construct one's own domain parameters, one should select the underlying field and then use one of the following strategies to find a curve with appropriate (i.e., near prime) number of points using one of the following methods:

- Select a random curve and use a general point-counting algorithm, for example, Schoof's algorithm or Schoof–Elkies–Atkin algorithm,
- Select a random curve from a family which allows easy calculation of the number of points (e.g., Koblitz curves), or
- Select the number of points and generate a curve with this number of points using
*complex multiplication*technique.^{[10]}

Several classes of curves are weak and should be avoided:

- Curves over with non-prime
*m*are vulnerable to Weil descent attacks.^{[11]}^{[12]} - Curves such that
*n*divides (where*p*is the characteristic of the field:*q*for a prime field, or for a binary field) for sufficiently small*B*are vulnerable to Menezes–Okamoto–Vanstone (MOV) attack^{[13]}^{[14]}which applies usual discrete logarithm problem (DLP) in a small-degree extension field of to solve ECDLP. The bound*B*should be chosen so that discrete logarithms in the field are at least as difficult to compute as discrete logs on the elliptic curve .^{[15]} - Curves such that are vulnerable to the attack that maps the points on the curve to the additive group of .
^{[16]}^{[17]}^{[18]}

### Key sizes[edit]

Because all the fastest known algorithms that allow one to solve the ECDLP (baby-step giant-step, Pollard's rho, etc.), need steps, it follows that the size of the underlying field should be roughly twice the security parameter. For example, for 128-bit security one needs a curve over , where . This can be contrasted with finite-field **cryptography** (e.g., DSA) which requires^{[19]} 3072-bit public keys and 256-bit private keys, and integer factorization **cryptography** (e.g., RSA) which requires a 3072-bit value of *n*, where the private key should be just as large. However, the public key may be smaller to accommodate efficient encryption, especially when processing power is limited.

The hardest ECC scheme (publicly) broken to date had a 112-bit key for the prime field case and a 109-bit key for the binary field case. For the prime field case, this was broken in July 2009 using a cluster of over 200 PlayStation 3 game consoles and could have been finished in 3.5 months using this cluster when running continuously.^{[20]} The binary field case was broken in April 2004 using 2600 computers over 17 months.^{[21]}

A current project is aiming at breaking the ECC2K-130 challenge by Certicom, by using a wide range of different hardware: CPUs, GPUs, FPGA.^{[22]}

### Projective coordinates[edit]

A close examination of the addition rules shows that in order to add two points, one needs not only several additions and multiplications in but also an inversion operation. The inversion (for given find such that ) is one to two orders of magnitude slower^{[23]} than multiplication. However, points on a curve can be represented in different coordinate systems which do not require an inversion operation to add two points. Several such systems were proposed: in the *projective* system each point is represented by three coordinates using the following relation: , ; in the *Jacobian system* a point is also represented with three coordinates , but a different relation is used: , ; in the *López–Dahab system* the relation is , ; in the *modified Jacobian* system the same relations are used but four coordinates are stored and used for calculations ; and in the *Chudnovsky Jacobian* system five coordinates are used . Note that there may be different naming conventions, for example, IEEE P1363-2000 standard uses "projective coordinates" to refer to what is commonly called Jacobian coordinates. An additional speed-up is possible if mixed coordinates are used.^{[24]}

### Fast reduction (NIST curves)[edit]

Reduction modulo *p* (which is needed for addition and multiplication) can be executed much faster if the prime *p* is a pseudo-Mersenne prime, that is ; for example, or Compared to Barrett reduction, there can be an order of magnitude speed-up.^{[25]} The speed-up here is a practical rather than theoretical one, and derives from the fact that the moduli of numbers against numbers near powers of two can be performed efficiently by computers operating on binary numbers with bitwise operations.

The curves over with pseudo-Mersenne *p* are recommended by NIST. Yet another advantage of the NIST curves is that they use *a* = −3, which improves addition in Jacobian coordinates.

According to Bernstein and Lange, many of the efficiency-related decisions in NIST FIPS 186-2 are sub-optimal. Other curves are more secure and run just as fast.^{[26]}

## Applications[edit]

Elliptic curves are applicable for encryption, digital signatures, pseudo-random generators and other tasks. They are also used in several integer factorization algorithms that have applications in **cryptography**, such as Lenstra elliptic curve factorization.

In 1999, NIST recommended fifteen elliptic curves. Specifically, FIPS 186-4^{[27]} has ten recommended finite fields:

- Five prime fields for certain primes
*p*of sizes 192, 224, 256, 384, and 521 bits. For each of the prime fields, one elliptic curve is recommended. - Five binary fields for
*m*equal 163, 233, 283, 409, and 571. For each of the binary fields, one elliptic curve and one Koblitz curve was selected.

The NIST recommendation thus contains a total of five prime curves and ten binary curves. The curves were ostensibly chosen for optimal security and implementation efficiency.^{[28]}

In 2013, *The New York Times* stated that Dual Elliptic Curve Deterministic Random Bit Generation (or Dual_EC_DRBG) had been included as a NIST national standard due to the influence of NSA, which had included a deliberate weakness in the algorithm and the recommended elliptic curve.^{[29]} RSA Security in September 2013 issued an advisory recommending that its customers discontinue using any software based on Dual_EC_DRBG.^{[30]}^{[31]} In the wake of the exposure of Dual_EC_DRBG as "an NSA undercover operation", **cryptography** experts have also expressed concern over the security of the NIST recommended elliptic curves,^{[32]} suggesting a return to encryption based on non-elliptic-curve groups.

Elliptic curve **cryptography** is used by the cryptocurrency Bitcoin.^{[33]}
Ethereum version 2.0 makes extensive use of elliptic curve pairs using BLS signatures—as specified in the IETF draft BLS specification—for cryptographically assuring that a specific Eth2 validator has actually verified a particular transaction.^{[34]}^{[35]}

## Security[edit]

### Side-channel attacks[edit]

Unlike most other DLP systems (where it is possible to use the same procedure for squaring and multiplication), the EC addition is significantly different for doubling (*P* = *Q*) and general addition (*P* ≠ *Q*) depending on the coordinate system used. Consequently, it is important to counteract side-channel attacks (e.g., timing or simple/differential power analysis attacks) using, for example, fixed pattern window (a.k.a. comb) methods^{[clarification needed]}^{[36]} (note that this does not increase computation time). Alternatively one can use an Edwards curve; this is a special family of elliptic curves for which doubling and addition can be done with the same operation.^{[37]} Another concern for ECC-systems is the danger of fault attacks, especially when running on smart cards.^{[38]}

### Backdoors[edit]

Cryptographic experts have expressed concerns that the National Security Agency has inserted a kleptographic backdoor into at least one elliptic curve-based pseudo random generator.^{[39]} Internal memos leaked by former NSA contractor, Edward Snowden, suggest that the NSA put a backdoor in the Dual EC DRBG standard.^{[40]} One analysis of the possible backdoor concluded that an adversary in possession of the algorithm's secret key could obtain encryption keys given only 32 bytes of PRNG output.^{[41]}

The SafeCurves project has been launched in order to catalog curves that are easy to securely implement and are designed in a fully publicly verifiable way to minimize the chance of a backdoor.^{[42]}

### Quantum computing attacks[edit]

Shor's algorithm can be used to break elliptic curve **cryptography** by computing discrete logarithms on a hypothetical quantum computer. The latest quantum resource estimates for breaking a curve with a 256-bit modulus (128-bit security level) are 2330 qubits and 126 billion Toffoli gates.^{[43]} In comparison, using Shor's algorithm to break the RSA algorithm requires 4098 qubits and 5.2 trillion Toffoli gates for a 2048-bit RSA key, suggesting that ECC is an easier target for quantum computers than RSA. All of these figures vastly exceed any quantum computer that has ever been built, and estimates place the creation of such computers as a decade or more away.^{[citation needed]}

Supersingular Isogeny Diffie–Hellman Key Exchange provides a post-quantum secure form of elliptic curve **cryptography** by using isogenies to implement Diffie–Hellman key exchanges. This key exchange uses much of the same field arithmetic as existing elliptic curve **cryptography** and requires computational and transmission overhead similar to many currently used public key systems.^{[44]}

In August 2015, the NSA announced that it planned to transition "in the not distant future" to a new cipher suite that is resistant to quantum attacks. "Unfortunately, the growth of elliptic curve use has bumped up against the fact of continued progress in the research on quantum computing, necessitating a re-evaluation of our cryptographic strategy."^{[3]}

### Invalid curve attack[edit]

When ECC is used in virtual machines, an attacker may use an invalid curve to get a complete PDH private key.^{[45]}

## Patents[edit]

At least one ECC scheme (ECMQV) and some implementation techniques are covered by patents.

## Alternative representations[edit]

Alternative representations of elliptic curves include:

- Hessian curves
- Edwards curves
- Twisted curves
- Twisted Hessian curves
- Twisted Edwards curve
- Doubling-oriented Doche–Icart–Kohel curve
- Tripling-oriented Doche–Icart–Kohel curve
- Jacobian curve
- Montgomery curves

## See also[edit]

- Cryptocurrency
- Curve25519
- FourQ
- DNSCurve
- RSA (cryptosystem)
- ECC patents
- Elliptic curve Diffie-Hellman (ECDH)
- Elliptic Curve Digital Signature Algorithm (ECDSA)
- EdDSA
- ECMQV
- Elliptic curve point multiplication
- Homomorphic Signatures for Network Coding
- Hyperelliptic curve
**cryptography** - Pairing-based
**cryptography** - Public-key
**cryptography** - Quantum
**cryptography** - Supersingular isogeny key exchange

## Notes[edit]

**^**Commercial National Security Algorithm Suite and Quantum Computing FAQ U.S. National Security Agency, January 2016.**^**"Fact Sheet NSA Suite B**Cryptography**".*U.S. National Security Agency*. Archived from the original on 2009-02-07.- ^
^{a}^{b}"Commercial National Security Algorithm Suite".*www.nsa.gov*. 19 August 2015. Archived from the original on 2019-06-04. Retrieved 2020-01-08. **^**RSA Laboratories. "6.3.4 Are elliptic curve cryptosystems patented?". Archived from the original on 2016-11-01.**^**Bernstein, D. J. "Irrelevant patents on elliptic-curve**cryptography**".- ^
^{a}^{b}"The Case for Elliptic Curve**Cryptography**".*NSA*. Archived from the original on 2009-01-17. **^**Koblitz, N. (1987). "Elliptic curve cryptosystems".*Mathematics of Computation*.**48**(177): 203–209. doi:10.2307/2007884. JSTOR 2007884.**^**Miller, V. (1985). "Use of elliptic curves in**cryptography**".*Advances in Cryptology — CRYPTO '85 Proceedings*.*CRYPTO*. Lecture Notes in Computer Science.**85**. pp. 417–426. doi:10.1007/3-540-39799-X_31. ISBN 978-3-540-16463-0.**^**"GEC 2: Test Vectors for SEC 1" (PDF).*www.secg.org*. Archived from the original (PDF download) on 2013-06-06.**^**Lay, Georg-Johann; Zimmer, Horst G. (1994). "Constructing elliptic curves with given group order over large finite fields".*Algorithmic Number Theory*. Lecture Notes in Computer Science.**877**. pp. 250–263. doi:10.1007/3-540-58691-1_64. ISBN 978-3-540-58691-3.**^**Galbraith, S. D.; Smart, N. P. (1999). "A Cryptographic Application of Weil Descent".*A cryptographic application of the Weil descent*.. Lecture Notes in Computer Science.**Cryptography**and Coding**1746**. p. 799. doi:10.1007/3-540-46665-7_23. ISBN 978-3-540-66887-9. S2CID 15134380.**^**Gaudry, P.; Hess, F.; Smart, N. P. (2000). "Constructive and destructive facets of Weil descent on elliptic curves" (PDF).*Hewlett Packard Laboratories Technical Report*.**^**Menezes, A.; Okamoto, T.; Vanstone, S. A. (1993). "Reducing elliptic curve logarithms to logarithms in a finite field".*IEEE Transactions on Information Theory*.**39**(5): 1639–1646. doi:10.1109/18.259647.**^**Hitt, L. (2006). "On an Improved Definition of Embedding Degree".*IACR ePrint Report*.**415**.**^**IEEE P1363, section A.12.1**^**Semaev, I. (1998). "Evaluation of discrete logarithm in a group of*p*-torsion points of an elliptic curve in characteristic*p*".*Mathematics of Computation*.**67**(221): 353–356. Bibcode:1998MaCom..67..353S. doi:10.1090/S0025-5718-98-00887-4.**^**Smart, N. (1999). "The discrete logarithm problem on elliptic curves of trace one".*Journal of Cryptology*.**12**(3): 193–196. CiteSeerX 10.1.1.17.1880. doi:10.1007/s001459900052. S2CID 24368962.**^**Satoh, T.; Araki, K. (1998). "Fermat quotients and the polynomial time discrete log algorithm for anomalous elliptic curves".*Commentarii Mathematici Universitatis Sancti Pauli*.**47**.**^**NIST, Recommendation for Key Management—Part 1: general, Special Publication 800-57, August 2005.**^**"112-bit prime ECDLP solved – LACAL".*lacal.epfl.ch*. Archived from the original on 2009-07-15. Retrieved 2009-07-11.**^**"Certicom Announces Elliptic Curve**Cryptography**Challenge Winner".*Certicom*. April 27, 2004. Archived from the original on 2011-07-19.**^**"Breaking ECC2K-130".*www.ecc-challenge.info*.**^**Hitchcock, Y.; Dawson, E.; Clark, A.; Montague, P. (2002). "Implementing an efficient elliptic curve cryptosystem over GF(p) on a smart card" (PDF).*ANZIAM Journal*.**44**. Archived from the original (PDF) on 2006-03-27.**^**Cohen, H.; Miyaji, A.; Ono, T. (1998).*Efficient Elliptic Curve Exponentiation Using Mixed Coordinates*.*Advances in Cryptology – AsiaCrypt '98*. Lecture Notes in Computer Science.**1514**. pp. 51–65. doi:10.1007/3-540-49649-1_6. ISBN 978-3-540-65109-3.**^**Brown, M.; Hankerson, D.; Lopez, J.; Menezes, A. (2001).*Software Implementation of the NIST Elliptic Curves Over Prime Fields*.*Topics in Cryptology – CT-RSA 2001*. Lecture Notes in Computer Science.**2020**. pp. 250–265. CiteSeerX 10.1.1.25.8619. doi:10.1007/3-540-45353-9_19. ISBN 978-3-540-41898-6.**^**Daniel J. Bernstein & Tanja Lange. "SafeCurves: choosing safe curves for elliptic-curve**cryptography**". Retrieved 1 December 2013.**^**Technology, National Institute of Standards and (2013-07-19). "Digital Signature Standard (DSS)". Cite journal requires`|journal=`

(help)**^**FIPS PUB 186-3, Digital Signature Standard (DSS).**^**Perlroth, Nicole; Larson, Jeff; Shane, Scott (2013-09-05). "N.S.A. Able to Foil Basic Safeguards of Privacy on Web".*New York Times*. Retrieved 28 October 2018.**^**Kim Zetter, RSA Tells Its Developer Customers: Stop Using NSA-Linked Algorithm*Wired*, 19 September 2013. "Recommending against the use of SP 800-90A Dual Elliptic Curve Deterministic Random Bit Generation: NIST strongly recommends that, pending the resolution of the security concerns and the re-issuance of SP 800-90A, the Dual_EC_DRBG, as specified in the January 2012 version of SP 800-90A, no longer be used."**^**"Search – CSRC".*csrc.nist.gov*.**^**Bruce Schneier (5 September) "I no longer trust the constants. I believe the NSA has manipulated them through their relationships with industry." See Are the NIST Standard Elliptic Curves Back-doored?,*Slashdot*, 11 September 2013.**^**"Mastering Bitcoin 2nd Edition – Andreas M. Antonopoulos".*github.com*. 2018-10-05.**^**"Ethereum 2.0 Phase 0 -- The Beacon Chain : BLS Signatures". 28 July 2020. Retrieved 4 September 2020.**^**Dan Boneh; Ben Lynn & Hovav Shacham (2004). "Short Signatures from the Weil Pairing".*Journal of Cryptology*.**17**(4): 297–319. CiteSeerX 10.1.1.589.9141. doi:10.1007/s00145-004-0314-9. S2CID 206885645.**^**Hedabou, M.; Pinel, P.; Beneteau, L. (2004). "A comb method to render ECC resistant against Side Channel Attacks" (PDF). Cite journal requires`|journal=`

(help)**^**"Cr.yp.to: 2014.03.23: How to design an elliptic-curve signature system".**^**See, for example, Biehl, Ingrid; Meyer, Bernd; Müller, Volker (2000).*Differential Fault Attacks on Elliptic Curve Cryptosystems*(PDF).*Advances in Cryptology – CRYPTO 2000*. Lecture Notes in Computer Science.**1880**. pp. 131–146. doi:10.1007/3-540-44598-6_8. ISBN 978-3-540-67907-3.**^**"Did NSA Put a Secret Backdoor in New Encryption Standard?".*www.schneier.com*.**^**"Government Announces Steps to Restore Confidence on Encryption Standards".*NY Times – Bits Blog*. 2013-09-10. Retrieved 2015-11-06.**^**http://rump2007.cr.yp.to/15-shumow.pdf**^**Bernstein, Daniel J.; Lange, Tanja. "SafeCurves: choosing safe curves for elliptic-curve**cryptography**". Retrieved October 1, 2016.**^**Roetteler, Martin; Naehrig, Michael; Svore, Krysta M.; Lauter, Kristin (2017). "Quantum resource estimates for computing elliptic curve discrete logarithms". arXiv:1706.06752 [quant-ph].**^**De Feo, Luca; Jao, Plut (2011). "Towards quantum-resistant cryptosystems from supersingular elliptic curve isogenies".*Cryptology ePrint Archive, Report 2011/506*. IACR. Archived from the original on 2014-05-03. Retrieved 3 May 2014.**^**Cohen, Cfir (25 June 2019). "AMD-SEV: Platform DH key recovery via invalid curve attack (CVE-2019-9836)".*Seclist Org*. Archived from the original on 2 July 2019. Retrieved 4 July 2019.The SEV elliptic-curve (ECC) implementation was found to be vulnerable to an invalid curve attack. At launch-start command, an attacker can send small order ECC points not on the official NIST curves, and force the SEV firmware to multiply a small order point by the firmware’s private DH scalar.

## References[edit]

- Standards for Efficient
**Cryptography**Group (SECG), SEC 1: Elliptic Curve**Cryptography**, Version 1.0, September 20, 2000. (archived as if Nov 11, 2014) - D. Hankerson, A. Menezes, and S.A. Vanstone,
*Guide to Elliptic Curve*, Springer-Verlag, 2004.**Cryptography** - I. Blake, G. Seroussi, and N. Smart,
*Elliptic Curves in*, London Mathematical Society 265, Cambridge University Press, 1999.**Cryptography** - I. Blake, G. Seroussi, and N. Smart, editors,
*Advances in Elliptic Curve*, London Mathematical Society 317, Cambridge University Press, 2005.**Cryptography** - L. Washington,
*Elliptic Curves: Number Theory and*, Chapman & Hall / CRC, 2003.**Cryptography** - The Case for Elliptic Curve
**Cryptography**, National Security Agency (archived January 17, 2009) - Online Elliptic Curve
**Cryptography**Tutorial, Certicom Corp. (archived here as of March 3, 2016) - K. Malhotra, S. Gardner, and R. Patz, Implementation of Elliptic-Curve
**Cryptography**on Mobile Healthcare Devices, Networking, Sensing and Control, 2007 IEEE International Conference on, London, 15–17 April 2007 Page(s):239–244 - Saikat Basu, A New Parallel Window-Based Implementation of the Elliptic Curve Point Multiplication in Multi-Core Architectures, International Journal of Network Security, Vol. 13, No. 3, 2011, Page(s):234–241 (archived here as of March 4, 2016)
- Christof Paar, Jan Pelzl, "Elliptic Curve Cryptosystems", Chapter 9 of "Understanding
**Cryptography**, A Textbook for Students and Practitioners". (companion web site contains online**cryptography**course that covers elliptic curve**cryptography**), Springer, 2009. (archived here as of April 20, 2016) - Luca De Feo, David Jao, Jerome Plut, Towards quantum-resistant cryptosystems from supersingular elliptic curve isogenies, Springer 2011. (archived here as of May 7, 2012)

## External links[edit]

Wikimedia Commons has media related to .Elliptic curve |