[*] up [*] contents
Next: Bibliography Up: Finite Fields and Zech's Previous: 6. Efficient exponents   Contents

7. Discussion

Building tables for Zech's logarithm requires a lot of space and time at least proportional to the size of corresponding field. In theory of coding such algorithms are called exponential, since order of magnitudes are compared with the degree of the field, as a measure of the length of elementary messages.

Thus these tables are not an Ğimmediateğ tool for code breaking, and related problems. But allowing fast calculus in some subfields is ever welcome, and can be a piece of some more sophisticated attack.

Let us discuss maximal field size that can be attained. Storing in internal memory some table of natural integers is easy up to some mega-octets, leading to \( m\leq 20 \). With the Huber's method, a space/time bargain can be done with factor \( 6m \). Thus, only \( 1.3\, Mo \) are requested for \( m=26 \) and \( 2.5\, Mo \) for \( m=27 \).

For multiplications, divisions or exponentiations in \( \mathrm{GF}\! \left( 2^{31} \right) \), a storage capacity of \( 46\, Mo \) will be requested, with \( 6m/2=93 \) storage accesses in the average case, or a capacity of \( 276\, Mo \) with \( 15 \) accesses. It i clear that, at the present moment, such a field's size is rather beyond the limits of general purpose hardware. For comparison, a VLSI processor specially designed for computing in \( \mathrm{GF}\! \left( 2^{155} \right) \) [1], enables multiplications and inversions in, respectively, 4 and 70 \ensuremath{µ}s.


[*] up [*] contents
Next: Bibliography Up: Finite Fields and Zech's Previous: 6. Efficient exponents   Contents
douillet@cnam.fr
2001-02-25