# Elliptic curve only hash

**The elliptic curve only hash (ECOH)** algorithm was submitted as a candidate for SHA-3 in the NIST hash function competition. However, it was rejected in the beginning of the competition since a was found.

The ECOH is based on the , that has not yet been successfully . However, MuHASH is too inefficient for practical use and changes had to be made. The main difference is that where MuHASH applies a random oracle , ECOH applies a function. Assuming random oracles, finding a in MuHASH implies solving the . MuHASH is thus a , i.e. we know that finding a collision is at least as some hard known mathematical problem.

ECOH does not use random oracles and its security is not strictly directly related to the discrete logarithm problem, yet it is still based on mathematical functions. ECOH is related to the Semaev’s problem of finding low degree solutions to the summation polynomial equations over binary field, called the **Summation Polynomial Problem**. An efficient algorithm to solve this problem has not been given so far. Although the problem was not proven to be , it is assumed that such an algorithm does not exist. Under certain assumptions, finding a collision in ECOH may be also viewed as an instance of the . Besides solving the Summation Polynomial Problem, there exists another way how to find second pre-images and thus collisions, **Wagner’s generalized birthday attack**.

ECOH is a nice example of hash function that is based on mathematical functions (with the approach) rather than on classical ad hoc mixing of bits to obtain the hash.

## Contents

## The algorithm

Given , ECOH divides the message into blocks . If the last block is incomplete, it is padded with single 1 and then appropriate number of 0. Let furthermore be a function that maps a message block and an integer to an elliptic curve point. Then using the mapping , each block is transformed to an point , and these points are together with two more points. One additional point contains the padding and depends only on the message length. The second additional point depends on the message length and the XOR of all message blocks. The result is to get the hash .

The two extra points are computed by and . adds all the elliptic curve points and the two extra points together. Finally, the result is passed through an output transformation function f to get the hash result . To read more about this algorithm, see “ECOH: the Elliptic Curve Only Hash”.

### Examples

Four ECOH algorithms were proposed, ECOH-224, ECOH-256, ECOH-384 and ECOH-512. The number represents the size of the message digest. They differ in the length of parameters, block size and in the used elliptic curve. The first two uses the elliptic curve B-283: , with parameters (128, 64, 64). ECOH-384 uses the curve B-409: , with parameters (192, 64, 64). ECOH-512 uses the curve B-571: , with parameters (256, 128, 128). It can hash messages of bit length up to .

## Properties

**Incrementality**: ECOH of a message can be updated quickly, given a small change in the message and an intermediate value in ECOH computation.**Parallelizability**: This means the computation of the can be done on parallel systems.-
**Speed**: The ECOH algorithm is about thousand times slower than SHA-1. However, given the developments in desktop hardware towards and , ECOH may in a few years be as fast as SHA-1 for long messages. For short messages, ECOH is relatively slow, unless extensive tables are used.

## Security of ECOH

The ECOH hash functions are based on concrete mathematical functions. They were designed such that the problem of finding collisions should be to a known and hard mathematical problem (the ). It means that if one could find collisions, one would be able to solve the underlying mathematical problem which is assumed to be hard and unsolvable in . Functions with these properties are known and are quite unique among the rest of hash functions. Nevertheless, second pre-image (and thus a collision) was later found because the assumptions given in the proof were too strong.

### Semaev Summation Polynomial

One way of finding collisions or second pre-images is solving **Semaev Summation Polynomials**. For a given elliptic curve E, there exists polynomials that are symmetric in variables and that vanish exactly when evaluated at abscissae of points whose sum is 0 in . So far, an efficient algorithm to solve this problem does not exist and it is assumed to be hard (but not proven to be ).

More formally: Let be a finite field, be an elliptic curve with having coefficients in and be the point of infinity. It is known that there exists a multivariable polynomial if and only if there exist < such that . This polynomial has degree in each variable. The problem is to find this polynomial.

### Provable security discussion

The problem of finding collisions in ECOH is similar to the . Solving a subset sum problem is almost as hard as the problem. It is generally assumed that this is not doable in . However a significantly loose heuristic must be assumed, more specifically, one of the involved parameters in the computation is not necessarily random but has a particular structure. If one adopts this loose heuristic, then finding an internal ECOH collision may be viewed as an instance of the .

A second pre-image attack exists in the form of generalized birthday attack.

### Second pre-image attack

**Description of the attack**: This is a Wagnerâ€™s Generalized . It requires 2^{143} time for ECOH-224 and ECOH-256, 2^{206} time for ECOH-384, and 2^{287} time for ECOH-512. The attack sets the checksum block to a fixed value and uses a collision search on the elliptic curve points. For this attack we have a message *M* and try to find a *M’* that hashes to the same message. We first split the message length into six blocks. So . Let *K* be a natural number. We choose *K* different numbers for and define by . We compute the *K* corresponding elliptic curve points and store them in a list. We then choose *K* different random values for , define , we compute , and store them in a second list. Note that the target *Q* is known. only depends on the length of the message which we have fixed. depends on the length and the XOR of all message blocks, but we choose the message blocks such that this is always zero. Thus, is fixed for all our tries.

If *K* is larger than the square root of the number of points on the elliptic curve then we expect one between the two lists. This gives us a message with: This means that this message leads to the target value *Q* and thus to a second preimage, which was the question. The workload we have to do here is two times *K* partial hash computations. For more info, see “A Second Pre-image Attack Against Elliptic Curve Only Hash (ECOH)”.

Actual parameters:

- ECOH-224 and ECOH-256 use the elliptic curve B-283 with approximately points on the curve. We choose and get an attack with complexity .
- ECOH-384 uses the elliptic curve B-409 with approximately points on the curve. Choosing gives an attack with complexity
- ECOH-512 uses the elliptic curve B-571 with approximately points on the curve. Choosing gives an attack with complexity

## ECOH2

The official comments on ECOH included a proposal called ECOH2 that doubles the elliptic curve size in an effort to stop the Halcrow-Ferguson second preimage attack with a prediction of improved or similar performance.