Elliptic Curve Point Multiplication

Elliptic curve scalar multiplication is the operation of successively adding a point along an elliptic curve to itself repeatedly. It is used in elliptic curve cryptography (ECC).
The literature presents this operation as scalar multiplication, as written in Hessian form of an elliptic curve. A widespread name for this operation is also elliptic curve point multiplication, but this can convey the wrong impression of being a multiplication between two points.

Basics

Given a curve, ''E'', defined by some equation in a finite field (such as ''E'': ), point multiplication is defined as the repeated addition of a point along that curve. Denote as for some scalar (integer) ''n'' and a point that lies on the curve, ''E''. This type of curve is known as a Weierstrass curve.

The security of modern ECC depends on the intractability of determining ''n'' from given known values of ''Q'' and ''P'' if ''n'' is large (known as the elliptic curve discrete logarithm problem by analogy to other cryptographic systems). This is because the addition of two points on an elliptic curve (or the addition of one point to itself) yields a third point on the elliptic curve whose location has no immediately obvious relationship to the locations of the first two, and repeating this many times over yields a point ''nP'' that may be essentially anywhere. Intuitively, this is not dissimilar to the fact that if you had a point ''P'' on a circle, adding 42.57 degrees to its angle may still be a point "not too far" from ''P'', but adding 1000 or 1001 times 42.57 degrees will yield a point that requires a bit more complex calculation to find the original angle. Reversing this process, i.e., given ''Q=nP'' and ''P'', and determining ''n'', can only be done by trying out all possible ''n''—an effort that is computationally intractable if ''n'' is large.

Point operations

There are three commonly defined operations for elliptic curve points: addition, doubling and negation.

Point at infinity

Point at infinity is the identity element of elliptic curve arithmetic. Adding it to any point results in that other point, including adding point at infinity to itself.
That is:
:$\begin \mathcal + \mathcal = \mathcal\\ \mathcal + P = P \end$

Point at infinity is also written as .

Point negation

Point negation is finding such a point, that adding it to itself will result in point at infinity ().
:$\begin P + (-P) = \mathcal \end$

For elliptic curves of the form ''E'': , negation is a point with the same ''x'' coordinate but negated ''y'' coordinate:
:$\begin (x, y) + (-(x, y)) &= \mathcal\\ (x, y) + (x, -y) &= \mathcal\\ (x, -y) &= -(x, y) \end$

Point addition

With 2 distinct points, ''P'' and ''Q'', addition is defined as the negation of the point resulting from the intersection of the curve, ''E'', and the straight line defined by the points ''P'' and ''Q'', giving the point, ''R''.
:$\begin P + Q &= R \\ (x_p, y_p) + (x_q, y_q) &= (x_r, y_r) \end$

Assuming the elliptic curve, ''E'', is given by , this can be calculated as:
:$\begin \lambda &= \frac \\ x_r &= \lambda^2 - x_p - x_q \\ y_r &= \lambda(x_p - x_r) - y_p \\ \end$
These equations are correct when neither point is the point at infinity, , and if the points have different x coordinates (they're not mutual inverses). This is important for the ECDSA verification algorithm where the hash value could be zero.

Point doubling

Where the points ''P'' and ''Q'' are coincident (at the same coordinates), addition is similar, except that there is no well-defined straight line through ''P'', so the operation is closed using a limiting case, the tangent to the curve, ''E'', at ''P''.

This is calculated as above, taking derivatives (dE/dx)/(dE/dy):
:$\lambda = \frac$

where ''a'' is from the defining equation of the curve, ''E'', above.

Point multiplication

The straightforward way of computing a point multiplication is through repeated addition. However, there are more efficient approaches to computing the multiplication.

Double-and-add

The simplest method is the double-and-add method, similar to square-and-multiply in modular exponentiation. The algorithm works as follows:

To compute ''sP'', start with the binary representation for ''s'': , where .
eA
* Iterative algorithm, index increasing:

let bits = bit_representation(s) # the vector of bits (from LSB to MSB) representing s
let res = $\begin\mathcal\end$ # point at infinity
let temp = P # track doubled P val
for bit in bits:
if bit

1:
res = res + temp # point add
temp = temp + temp # double
return res

* Iterative algorithm, index decreasing:

let bits = bit_representation(s) # the vector of bits (from LSB to MSB) representing s
let i = length(bits) - 2
let res = P
while (i >= 0): # traversing from second MSB to LSB
res = res + res # double
if bits

1:
res = res + P # add
i = i - 1
return res

Note that both of the iterative methods above are vulnerable to timing analysis. See Montgomery Ladder below for an alternative approach.

* Recursive algorithm:

algorithm f(P, d) is
if d = 0 then
return 0 # computation complete
else if d = 1 then
return P
else if d mod 2 = 1 then
return point_add(P, f(P, d - 1)) # addition when d is odd
else
return f(point_double(P), d / 2) # doubling when d is even

where ''f'' is the function for multiplying, ''P'' is the coordinate to multiply, ''d'' is the number of times to add the coordinate to itself. Example: ''100P'' can be written as ' and thus requires six point double operations and two point addition operations. ''100P'' would be equal to ''f(P, 100)''.

This algorithm requires log₂(''d'') iterations of point doubling and addition to compute the full point multiplication. There are many variations of this algorithm such as using a window, sliding window, NAF, NAF-w, vector chains, and Montgomery ladder.

Windowed method

In the windowed version of this algorithm, one selects a window size ''w'' and computes all $2^w$ values of $dP$ for $d = 0, 1, 2, \dots, 2^w - 1$. The algorithm now uses the representation $d = d_0 + 2^wd_1 + 2^d_2 + \cdots + 2^d_m$ and becomes

Q ← 0
for i from m to 0 do
Q ← point_double_repeat(Q, w)
if d_i > 0 then
Q ← point_add(Q, d_iP) # using pre-computed value of d_iP
return Q

This algorithm has the same complexity as the double-and-add approach with the benefit of using fewer point additions (which in practice are slower than doubling). Typically, the value of ''w'' is chosen to be fairly small making the pre-computation stage a trivial component of the algorithm. For the NIST recommended curves, $w = 4$ is usually the best selection. The entire complexity for a ''n''-bit number is measured as $n + 1$ point doubles and $2^w - 2 + \tfrac$ point additions.

Sliding-window method

In the sliding-window version, we look to trade off point additions for point doubles. We compute a similar table as in the windowed version except we only compute the points $dP$ for $d = 2^, 2^ + 1, \dots, 2^w - 1$. Effectively, we are only computing the values for which the most significant bit of the window is set. The algorithm then uses the original double-and-add representation of $d = d_0 + 2d_1 + 2^2d_2 + \cdots + 2^md_m$.

Q ← 0
for i from m downto 0 do
if d_i = 0 then
Q ← point_double(Q)
else
t ← extract j (up to w − 1) additional bits from d (including d_i)
i ← i − j
if j < w then
Perform double-and-add using t
return Q
else
Q ← point_double_repeat(Q, w)
Q ← point_add(Q, tP)
return Q

This algorithm has the benefit that the pre-computation stage is roughly half as complex as the normal windowed method while also trading slower point additions for point doublings. In effect, there is little reason to use the windowed method over this approach, except that the former can be implemented in constant time. The algorithm requires $w - 1 + n$ point doubles and at most $2^ - 1 + \tfrac$ point additions.

-ary non-adjacent form (NAF) method

In the non-adjacent form we aim to make use of the fact that point subtraction is just as easy as point addition to perform fewer (of either) as compared to a sliding-window method. The NAF of the multiplicand $d$ must be computed first with the following algorithm

i ← 0
while (d > 0) do
if (d mod 2) = 1 then
d_i ← d mods 2^w
d ← d − d_i
else
d_i = 0
d ← d/2
i ← i + 1
return (d_i−1, d_i-2, …, d₀)

Where the signed modulo function ''mods'' is defined as

if (d mod 2^w) >= 2^w−1
return (d mod 2^w) − 2^w
else
return d mod 2^w

This produces the NAF needed to now perform the multiplication. This algorithm requires the pre-computation of the points $\lbrace 1, 3, 5, \dots, 2^ - 1 \rbrace P$ and their negatives, where $P$ is the point to be multiplied. On typical Weierstrass curves, if $P = \lbrace x, y \rbrace$ then $-P = \lbrace x, -y \rbrace$. So in essence the negatives are cheap to compute. Next, the following algorithm computes the multiplication $dP$:

Q ← 0
for j ← i − 1 downto 0 do
Q ← point_double(Q)
if (d_j != 0)
Q ← point_add(Q, d_jP)
return Q

The wNAF guarantees that on average there will be a density of $\tfrac$ point additions (slightly better than the unsigned window). It requires 1 point doubling and $2^ - 1$ point additions for precomputation. The algorithm then requires $n$ point doublings and $\tfrac$ point additions for the rest of the multiplication.

One property of the NAF is that we are guaranteed that every non-zero element $d_i$ is followed by at least $w - 1$ additional zeroes. This is because the algorithm clears out the lower $w$ bits of $d$ with every subtraction of the output of the ''mods'' function. This observation can be used for several purposes. After every non-zero element the additional zeroes can be implied and do not need to be stored. Secondly, the multiple serial divisions by 2 can be replaced by a division by $2^w$ after every non-zero $d_i$ element and divide by 2 after every zero.

It has been shown that through application of a FLUSH+RELOAD side-channel attack on OpenSSL, the full private key can be revealed after performing cache-timing against as few as 200 signatures performed.

Montgomery ladder

The Montgomery ladder approach computes the point multiplication in a ''fixed'' number of operations. This can be beneficial when timing, power consumption, or branch measurements are exposed to an attacker performing a side-channel attack. The algorithm uses the same representation as from double-and-add.

R₀ ← 0
R₁ ← P
for i from m downto 0 do
if d_i = 0 then
R₁ ← point_add(R₀, R₁)
R₀ ← point_double(R₀)
else
R₀ ← point_add(R₀, R₁)
R₁ ← point_double(R₁)

// invariant property to maintain correctness
assert R₁

point_add(R₀, P)
return R₀

This algorithm has in effect the same speed as the double-and-add approach except that it computes the same number of point additions and doubles regardless of the value of the multiplicand ''d''. This means that at this level the algorithm does not leak any information through branches or power consumption.

However, it has been shown that through application of a FLUSH+RELOAD side-channel attack on OpenSSL, the full private key can be revealed after performing cache-timing against only one signature at a very low cost.

Rust code for Montgomery Ladder:

/// Constant operation point multiplication.
/// NOTE: not memory safe.
/// NOTE: not timing-side channel safe (not constant time).
/// * `s`: scalar value to multiply by
/// * multiplication is defined to be P₀ + P₁ + ... Pₛ
fn sec_mul(&mut self, s: big) -> E521

Constant time Montgomery ladder

The security of a cryptographic implementation is likely to face the threat of the so called timing attacks
which exploits the data-dependent timing characteristics of the implementation. Machines running cryptographic
implementations consume variable amounts of time to process different inputs and so the timings
vary based on the encryption key. To resolve this issue, cryptographic algorithms are implemented
in a way which removes data dependent variable timing characteristic from the implementation leading
to the so called constant-time implementations. Software implementations are considered to be constant-time in the
following sense as stated in: “''avoids all input-dependent branches, all input-dependent array''
''indices, and other instructions with input-dependent timings.''” The GitHub page lists coding rules
for implementations of cryptographic operations, and more generally for operations involving secret or
sensitive values.

The Montgomery ladder is an $x$-coordinate only algorithm for elliptic curve point multiplication
and is based on the double and add rules over a specific set of curves known as Montgomery curve. The algorithm has a conditional branching
such that the condition depends on a secret bit. So a straightforward implementation of the ladder won't be
constant time and has the potential to leak the secret bit. This problem has been addressed in literature
and several constant time implementations are known. The constant time Montgomery ladder algorithm is as given below which uses two functions CSwap and Ladder-Step. In the return value of the algorithm Z₂^p-2 is the value of Z₂⁻¹ computed using the Fermat's little theorem.

algorithm Montgomery-Ladder(x_P, n) is
input: An $l$-bit scalar $n$ and the $x$-coordinate $x_P$ of a point $P$.
output: $x$-coordinate of $nP$, the $n$-times scalar multiple of $P$.

X₁ ← x_P; X₂ ← 1; Z₂ ← 0; X₃ ← x_P; Z₃ ← 1
prevbit ← 0

for $i$ from $l-1$ downto 0 do
bit ← bit-value at index $i$ of $n$
b ← bit $\oplus$ prevbit
prevbit ← bit
($\langle$X₂,Z₂$\rangle$,$\langle$X₃,Z₃$\rangle$) ← CSwap($\langle$X₂,Z₂$\rangle$,$\langle$X₃,Z₃$\rangle$,b)
($\langle$X₂,Z₂$\rangle$,$\langle$X₃,Z₃$\rangle$) ← Ladder-Step($\langle$X₂,Z₂$\rangle$,$\langle$X₃,Z₃$\rangle$,X₁)

return X₂Z₂^p-2

The Ladder-Step function (given below) used within the ladder is the core of the algorithm and is a combined form of the differential add and doubling operations. The field
constant a₂₄ is defined as a₂₄ = $(A+2)/4$, where $A$ is a parameter of the underlying Montgomery curve.

Function Ladder-Step($\langle$X₂,Z₂$\rangle$,$\langle$X₃,Z₃$\rangle$,X₁)

T₁ ← X₂ + Z₂
T₂ ← X₂ - Z₂
T₃ ← X₃ + Z₃
T₄ ← X₃ - Z₃
T₅ ← T₁²
T₆ ← T₂²
T₂ ← T₂ · T₃
T₁ ← T₁ · T₄
T₁ ← T₁ + T₂
T₂ ← T₁ - T₂
X₃ ← T₁²
T₂ ← T₂²
Z₃ ← T₂ · X₁
X₂ ← T₅ · T₆
T₅ ← T₅ - T₆
T₁ ← a₂₄ · T₅
T₆ ← T₆ + T₁
Z₂ ← T₅ · T₆

return ($\langle$X₂,Z₂$\rangle$,$\langle$X₃,Z₃$\rangle$)

The CSwap function manages the conditional branching and helps the ladder to run following the requirements of a constant time implementation. The function swaps the pair of field elements $\langle$X₂,Z₂$\rangle$ and $\langle$X₃,Z₃$\rangle$ only if $b$ = 1 and
this is done without leaking any information about the secret bit. Various methods of implementing CSwap have been proposed in literature. A lesser costly option to manage the constant time requirement of the Montgomery ladder is conditional select which is formalised through a function CSelect. This function has been used in various optimisations and has been formally discussed in

Since the inception of the standard Montgomery curve Curve25519 at 128-bit security level, there has been various software implementations to compute the ECDH on various architectures and to achieve best possible performance cryptographic developers have resorted to write the implementations using assembly language of the underlying architecture. The work provided a couple of 64-bit assembly implementations targeting the AMD64 architecture. The implementations were developed using a tool known as ''qhasm'' which can generate high-speed assembly language cryptographic programs. It is to be noted that the function CSwap was used in the implementations of these ladders. After that there has been several attempts to optimise the ladder implementation through hand-written assembly programs out of which the notion of CSelect was first used in, Code available at https://github.com/armfazh/rfc7748_precomputed. and then in., Code available at https://github.com/kn-cs/x25519 Apart from using sequential instructions, vector instructions have also been used to optimise the ladder computation through various works., Coce available at https://github.com/armfazh/fld-ecc-vec, Code available at https://github.com/kn-cs/vec-ladder Along with AMD64, attempts have also been made to achieve efficient implementations on other architectures like ARM. The works and provides efficient implementations targeting the ARM architecture. The libraries lib25519 and are two state-of-art libraries containing efficient implementations of the Montgomery ladder for Curve25519. Nevertheless, the libraries have implementations of other cryptographic primitives as well.

Apart from Curve25519, there have been several attempts to compute the ladder over other curves at various security levels. Efficient implementations of the ladder over the standard curve Curve448 at 224-bit security level have also been studied in literature. A curve named Curve41417 providing security just over 200 bits was proposed in which a variant of Karatsuba strategy was used to implement the field multiplication needed for the related ECC software. In pursuit of searching Montgomery curves that are competitive to Curve25519 and Curve448 research has been done and couple of curves were proposed along with efficient sequential and vectorised implementations of the corresponding ladders. At 256-bit security level efficient implementations of the ladder have also been addressed through three different Montgomery curves., Code available at https://github.com/kn-cs/mont256-dh and https://github.com/kn-cs/mont256-vec

References

{{Reflist

Elliptic curves
Articles with example Rust code