| General | |
|---|---|
| Designers | S. Miyaguchi K. Ohta M. Iwata |
| First published | 1990 |
| Derived from | FEAL |
| Detail | |
| Digest sizes | 128 bits |
| Structure | Iterated hash function |
| Rounds | 8 |
In cryptography, N-hash is a cryptographic hash function based on the FEAL round function, and is now considered insecure. It was proposed in 1990 in an article by Miyaguchi, Ohta, and Iwata; [1] weaknesses were published the following year. [2]
N-hash has a 128-bit hash size. A message is divided into 128-bit blocks, and each block is combined with the hash value computed so far using the g compression function. g contains eight rounds, each of which uses an F function, similar to the one used by FEAL.
Eli Biham and Adi Shamir (1991) applied the technique of differential cryptanalysis to N-hash, and showed that collisions could be generated faster than by a birthday attack for N-hash variants with even up to 12 rounds. [2]
N-hash follows an early block cipher–based approach to cryptographic hash function design, in which the compression function is constructed from a cipher-like round function rather than from a dedicated hash-specific primitive. Such designs were common in the late 1980s and early 1990s, prior to the widespread adoption of purpose-built hash functions. [3] [4] [5] The chaining mechanism of N-hash combines the output of the round function with both the current message block and the previous hash state. This structure was later studied in the context of generic block cipher–based hash constructions and their resistance to known cryptanalytic techniques. [2] [6]
The cryptanalysis of N-hash highlighted the risks of directly reusing block cipher components in hash function design without sufficient security margins. Attacks on N-hash demonstrated that structural properties exploitable in encryption algorithms could also undermine collision resistance when applied in a hashing context. [2] [7] [8] As a result of these findings, N-hash was never adopted in practical cryptographic applications. It is cited primarily in academic literature as an early example that influenced later research into secure hash function construction and the separation of design principles for encryption and hashing. [9]