This page uses content from Wikipedia and is licensed under CC BY-SA.

**Trivium** is a synchronous stream cipher designed to provide a flexible trade-off between speed and gate count in hardware, and reasonably efficient software implementation.

Trivium was submitted to the Profile II (hardware) of the eSTREAM competition by its authors, Christophe De Cannière and Bart Preneel, and has been selected as part of the portfolio for low area hardware ciphers (Profile 2) by the eSTREAM project. It is not patented and has been specified as an International Standard under ISO/IEC 29192-3.^{[1]}

It generates up to 2^{64} bits of output from an 80-bit key and an 80-bit IV. It is the simplest eSTREAM entrant; while it shows remarkable resistance to cryptanalysis for its simplicity and performance, recent attacks leave the security margin looking rather slim.

Trivium's 288-bit internal state consists of three shift registers of different lengths. At each round, a bit is shifted into each of the three shift registers using a non-linear combination of taps from that and one other register; one bit of output is produced. To initialize the cipher, the key and IV are written into two of the shift registers, with the remaining bits starting in a fixed pattern; the cipher state is then updated 4 × 288 = 1152 times, so that every bit of the internal state depends on every bit of the key and of the IV in a complex nonlinear way.

No taps appear on the first 65 bits of each shift register, so each novel state bit is not used until at least 65 rounds after it is generated. This is the key to Trivium's software performance and flexibility in hardware.

Trivium may be specified very concisely using three recursive equations.^{[2]} Each variable is an element of GF(2); they can be represented as bits, with "+" being XOR and "•" being AND.

*a*_{i}=*c*_{i−66}+*c*_{i−111}+*c*_{i−110}•*c*_{i−109}+*a*_{i−69}*b*_{i}=*a*_{i−66}+*a*_{i−93}+*a*_{i−92}•*a*_{i−91}+*b*_{i−78}*c*_{i}=*b*_{i−69}+*b*_{i−84}+*b*_{i−83}•*b*_{i−82}+*c*_{i−87}

The output bits *r*_{0} ... *r*_{264−1} are then generated by

*r*_{i}=*c*_{i−66}+*c*_{i−111}+*a*_{i−66}+*a*_{i−93}+*b*_{i−69}+*b*_{i−84}

Given an 80-bit key *k*_{0} ... *k*_{79} and an *l*-bit IV *v*_{0} ... *v*_{l−1} (where 0 ≤ *l* ≤ 80), Trivium is initialized as follows:

- (
*a*_{−1245}...*a*_{−1153}) = (0, 0 ... 0,*k*_{0}...*k*_{79}) - (
*b*_{−1236}...*b*_{−1153}) = (0, 0 ... 0,*v*_{0}...*v*_{l−1}) - (
*c*_{−1263}...*c*_{−1153}) = (1, 1, 1, 0, 0 ... 0)

The large negative indices on the initial values reflect the 1152 steps that must take place before output is produced.

To map a stream of bits *r* to a stream of bytes *R*, we use the little-endian mapping *R*_{i} = Σ_{j=0 ... 7} 2^{j} *r*_{8i+j}.

A straightforward hardware implementation of Trivium would use 3488 logic gates and produce one bit per clock cycle. However, because each state bit is not used for at least 64 rounds, 64 state bits can be generated in parallel at a slightly greater hardware cost of 5504 gates. Different tradeoffs between speed and area are also possible.

The same property allows an efficient bitslice implementation in software; performance testing by eSTREAM give bulk encryption speeds of around 4 cycles/byte on some x86 platforms, which compares well to the 19 cycles/byte of the AES reference implementation on the same platform.

[Trivium] was designed as an exercise in exploring how far a stream cipher can be simplified without sacrificing its security, speed or ﬂexibility. While simple designs are more likely to be vulnerable to simple, and possibly devastating, attacks (which is why we strongly discourage the use of Trivium at this stage), they certainly inspire more confidence than complex schemes, if they survive a long period of public scrutiny despite their simplicity.

^{[3]}

As of April 2015^{[update]}, no cryptanalytic attacks better than brute force attack are known, but several attacks come close. The cube attack requires 2^{68} steps to break a variant of Trivium where the number of initialization rounds is reduced to 799.^{[4]} Previously other authors speculate that these techniques could lead to a break for 1100 initialisation rounds, or "maybe even the original cipher".^{[5]} This builds on an attack due to Michael Vielhaber that breaks 576 initialization rounds in only 2^{12.3} steps.^{[6]}^{[7]}

Another attack recovers the internal state (and thus the key) of the full cipher in around 2^{89.5} steps (where each step is roughly the cost of a single trial in exhaustive search).^{[8]} Reduced variants of Trivium using the same design principles have been broken using an equation-solving technique.^{[9]} These attacks improve on the well-known time-space tradeoff attack on stream ciphers, which with Trivium's 288-bit internal state would take 2^{144} steps, and show that a variant on Trivium which made no change except to increase the key length beyond the 80 bits mandated by eSTREAM Profile 2 would not be secure. Using optimised solving strategy, it is further possible to reduce the state-recovery complexity to 2^{132} steps.^{[10]}

A detailed justification of the design of Trivium is given in.^{[11]}

**^**ISO/IEC 29192-3:2012**^**eSTREAM Phorum, 2006-02-20**^**Christophe De Cannière, Bart Preneel (2005-04-29). "Trivium specifications" (PDF). eSTREAM submitted papers. Retrieved 2006-10-09.**^**Fouque, Pierre-Alain; Vannet, Thomas (2015-04-05). "Improving Key Recovery to 784 and 799 rounds of Trivium using Optimized Cube Attacks" (PDF). Cryptology ePrint Archive. ePrint 20150406:231124. Retrieved 2015-04-17.**^**Dinur, Itai; Shamir, Adi (2008-09-13). "Cube Attacks on Tweakable Black Box Polynomials" (PDF). Cryptology ePrint Archive. ePrint 20080914:160327. Retrieved 2008-12-04.**^**Michael Vielhaber (2007-10-28). "Breaking ONE.FIVIUM by AIDA an Algebraic IV Differential Attack".**^**Michael Vielhaber (2009-02-23). "Shamir's "cube attack": A Remake of AIDA, The Algebraic IV Differential Attack" (PDF).^{[permanent dead link]}**^**Alexander Maximov, Alex Biryukov (2007-01-23). "Two Trivial Attacks on Trivium" (PDF). Cryptology ePrint. (Table 6, page 11)**^**Håvard Raddum (2006-03-27). "Cryptanalytic results on Trivium" (PostScript). eSTREAM submitted papers. Retrieved 2006-10-09.**^**Pavol Zajac (2012-08-01). "Solving Trivium-based Boolean Equations Using the Method of Syllogisms". IOS Press.**^**Christophe De Cannière, Bart Preneel (2006-01-02). "Trivium - A Stream Cipher Construction Inspired by Block Cipher Design Principles" (PDF). eSTREAM submitted papers. Retrieved 2006-10-09.