MMH-Badger MAC

Badger is a Message Authentication Code (MAC) based on the idea of universal hashing and was developed by Boesgaard, Christensen, and Zenner.[1] It is constructed by strengthening the ∆-universal hash family MMH using an ϵ-almost strongly universal (ASU) hash function family after the application of ENH (see below), where the value of ϵ is 1/(2^{32}-5).[2] Since Badger is a MAC function based on the universal hash function approach, the conditions needed for the security of Badger are the same as those for other universal hash functions such as UMAC.

Introduction

The Badger MAC processes a message of length up to 2^{64}-1 bits and returns an authentication tag of length u\cdot32 bits, where 1\le u \le 5 . According to the security needs, user can choose the value of u, that is the number of parallel hash trees in Badger. One can choose larger values of u, but those values do not influence further the security of MAC. The algorithm uses a 128-bit key and the limited message length to be processed under this key is 2^{64}.[3]

The key setup has to be run only once per key in order to run the Badger algorithm under a given key, since the resulting internal state of the MAC can be saved to be used with any other message that will be processed later.

ENH


Hash families can be combined in order to obtain new hash families. For the ϵ-AU, ϵ-A∆U, and ϵ-ASU families, the latter are contained in the former. For instance, an A∆U family is also an AU family, an ASU is also an A∆U family, and so forth. On the other hand, a stronger family can be reduced to a weaker one, as long as a performance gain can be reached. A method to reduce ∆-universal hash function to universal hash functions will be described in the following.

Theorem 2[1]

Let H^\triangle be an ϵ-AΔU hash family from a set A to a set B. Consider a message (m, m_b) \in A \times B . Then the family H consisting of the functions h(m,m_b) = H^\triangle (m) + m_b is ϵ-AU.

If  m \ne m', then the probability that h(m,m_b) =h(m',m'_b) is at most ϵ, since H^\triangle is an ϵ-A∆U family. If  m = m' but  m_b\ne m_b', then the probability is trivially 0. The proof for Theorem 2 was described in [1]

The ENH-family is constructed based on the universal hash family NH (which is also used in UMAC):

NH_K (M)= \sum_{i=1}^ \frac{\ell}{2} (k_{(2i-1)} +_w m_{(2i-1)})\times (k_{2i} +_w m_{2i} )  \mod 2^{2w}

Where ‘+_w’ means ‘addition modulo 2^w’, and m_i,k_i \in \big\{0,\ldots, 2^w-1\big\}. It is a 2^{-w}-A∆U hash family.

Lemma 1[1]

The following version of NH is 2^{-w}-A∆U:

NH_K (M)=(k_1 +_w m_1 )\times(k_2 +_w m_2 )  \mod 2^{2w}

Choosing w=32 and applying Theorem 1, one can obtain the 2^{-32}-AU function family ENH, which will be the basic building block of the badger MAC:

ENH_{k_1,k_2} (m_1,m_2,m_3,m_4 )=(m_1 +_{32} k_1)(m_2 +_{32} k_2) +_{64} m_3 +_{64} 2^{32} m_4

where all arguments are 32-bits long and the output has 64-bits.

Construction

Badger is constructed using the strongly universality hash family and can be described as

\mathcal{H}=H^* \times F,[1]

where an \epsilon_{H^*}-AU universal function family H* is used to hash messages of any size onto a fixed size and an \epsilon_{F}-ASU function family F is used to guarantee the strong universality of the overall construction. NH and ENH are used to construct H*. The maximum input size of the function family H* is 2^{64}-1 and the output size is 128 bits, split into 64 bits each for the message and the hash. The collision probability for the H*-function ranges from 2^{-32} to 2^{-26.14}. To construct the strongly universal function family F, the ∆-universal hash family MMH* is transformed into a strongly universal hash family by adding another key.

Two steps on Badger

There are two steps that have to be executed for every message: processing phase and finalize phase.

Processing phase[3] In this phase, the data is hashed to a 64-bit string. A core function h : \big\{0,1\big\}^{64}\times \big\{0,1\big\}^{128} \to \big\{0,1\big\}^{64} is used in this processing phase, that hashes a 128-bit string  m_2 \parallel m_1 to a 64-bit string  h( k, m_2, m_1 ) as follows:

 h(k, m_2, m_1 )= (L(m_1 ) +_{32} L(k) )\cdot(U(m_1 ) +_{32} U(k) ) +_{64} m_2 \,

for any n, +_n means addition modulo 2^n. Given a 2n-bit string x, L(x) means least significant n bits, and U(x) means most significant n bits.

A message can be processed by using this function. Denote level_key [j][i] by k_j^i.

Pseudo-code of the processing phase is as follow.

L=|M|
if L=0
M^1=⋯=M^u=0
Go to finalization
r=L mod 64
if r≠0:
M=0^(64-r)∥M
for i=1 to u:
M^i=M
v^'=max{1,⌈log_2 L⌉-6}
for j=1 to v^':
divide M^i into 64-bit blocks, M^i=m_t^i∥⋯∥m_1^i
if t is even:
M^i=h(k_j^i,m_t^i,m_(t-1)^i )∥⋯∥h(k_j^i,m_2^i,m_1^i )
else
M^i=m_t^i∥h(k_j^i,m_(t-1)^i,m_(t-2)^i )∥⋯∥h(k_j^i,m_2^i,m_1^i )

Finalize phase[3] In this phase, the 64-string resulting from the processing phase is transformed into the desired MAC tag. This finalization phase uses the Rabbit stream cipher and uses both key setup and IV setup by taking the finalization key final_key[j][i] as k_j^i.

Pseudo-code of the finalization phase

RabbitKeySetup(K)
RabbitIVSetup(N)
for i=1 to u:
Q^i=0^7∥L∥M^i
divide Q^i into 27-bit blocks, Q^i=q_5^i∥⋯∥q_1^i
S^i=(∑_(j=1)^5 (q_j^i K_j^i))+K_6^i mod p
S=S^u∥⋯∥S^1
S=S ⨁ RabbitNextbit(u∙32)
return S

Notation:

From the pseudocode above, k denotes the key in the Rabbit Key Setup(K) which initializes Rabbit with the 128-bit key k. M denotes the message to be hashed and |M| denotes the length of the message in bits. q_i denotes a message M that is divided into i blocks. For the given 2n-bit string x then L(x) and U(x) respectively denoted its least significant n bits and most significant n bits.

Performance

Boesgard, Christensen and Zenner report the performance of Badger measured on a 1.0 GHz Pentium III and on a 1.7 GHz Pentium 4 processor.[1] The speed-optimized versions were programmed in assembly language inlined in C and compiled using the Intel C++ 7.1 compiler.

The following table presents Badger's properties for various restricted message lengths. “Memory req.” denotes the amount of memory required to store the internal state including key material and the inner state of the Rabbit stream cipher . “Setup” denotes the key setup, and “Fin.” denotes finalization with IV-setup.

Max. Message Size Forgery Bound Memory Reg. Setup Pentium III Fin. Pentium III Setup Pentium III Fin. Pentium III
2^{11} bytes (e.g.IPsec) 2^{-57.7} 400 bytes 1133 cycles 409 cycles 1774 cycles 776 cycles
2^{15} bytes (e.g.TLS) 2^{-56.6} 528 bytes 1370 cycles 421 cycles 2100 cycles 778 cycles
2^{32} bytes 2^{-54.2} 1072 bytes 2376 cycles 421 cycles 3488 cycles 778 cycles
2^{61}-1 bytes 2^{-52.2} 2000 bytes 4093 cycles 433 cycles 5854 cycles 800 cycles

MMH (Multilinear Modular Hashing)

The name MMH stands for Multilinear-Modular-Hashing. Applications in Multimedia are for example to verify the integrity of an on-line multimedia title. The performance of MMH is based on the improved support of integer scalar products in modern microprocessors.

MMH uses single precision scalar products as its most basic operation. It consists of a (modified) inner product between the message and a key modulo a prime p. The construction of MMH works in the finite field F_p for some prime integer p.

MMH*

MMH* involves a construction of a family of hash functions consisting of multilinear functions on F_p^k for some positive integer k. The family MMH* of functions from F_p^k to F_p is defined as follows.

 \mathrm{MMH}^* = \{ g_x : F_p^k \rightarrow F_p | x \in F_p^k \} \,

where x, m are vectors, and the functions g_x are defined as follows.

\!g_x(m) =  m x\mod p =  \sum_{i=1}^n  m_i\,x_i\mod p

In the case of MAC, m is a message and  x is a key where  m = (m_1,\ldots,m_k) and x = (x_1,\ldots,x_k), x_i, m_i \in \!F_p.

MMH* should satisfy the security requirements of a MAC, enabling say Ana and Bob to communicate in an authenticated way. They have a secret key x. Say Charles listens to the conversation between Ana and Bob and wants to change the message into his own message to Bob which should pass as a message from Ana. So, his message m' and Ana's message m will differ in at least one bit (e.g.  m_1 \ne m'_1 ).

Assume that Charles knows that the function is of the form  g_x (m) and he knows Ana's message  m but he does not know the key x then the probability that Charles can change the message or send his own message can be explained by the following theorem.

Theorem 1[4]:The family MMH* is ∆-universal.

Proof:

Take a\in F_p, and let  m , m' be two different messages. Assume without loss of generality that  m_1 \ne m'_1 . Then for any choice of  x_2,x_3,\ldots,x_s , there is


\begin{align}
{\Pr}_{x_1}[g_x (m)-g_x (m')\equiv a \mod p] &= {\Pr}_{x_1}[(m_1 x_1+m_2 x_2+ \cdots +m_k x_k )-(m'_1 x_1+m'_2 x_2+\cdots+m'_k x_k )\equiv a \mod p]\\
&= {\Pr}_{x_1}[(m_1-m'_1)x_1+(m_2-m'_2)x_2+ \cdots +(m_k-m'_k)x_k]\equiv a \mod p]\\
&= {\Pr}_{x_1}[(m_1-m'_1)x_1+\textstyle \sum_{k=2}^s(m_k-m'_k)x_k\equiv a \mod p]\\
&= {\Pr}_{x_1}[(m_1-m'_1)x_1\equiv a - \textstyle \sum_{k=2}^s(m_k-m'_k)x_k \mod p]\\
&=\frac {1}{p}
\end{align}

To explain the theorem above, take  F_p for  p prime represent the field as  F_p = \underbrace{\big\{ 0,1,\ldots,p-1 \big\}}_p . If one takes an element in  F_p , let say  0\in  F_p then the probability that  x_1=0 is

 {\Pr}_{x_1 \in \!{F_p}}(x_1=0)= \frac {1}{p}

So, what one actually needs to compute is

 {\Pr}_{(x_1,\ldots,x_k)\in \!{F_p^k}} (g_x(m)\equiv g_x(m')\mod p)

But,


\begin{align}
{\Pr}_{(x_1,\ldots,x_k)\in \!{F_p^k}}(g_x(m)\equiv g_x(m')\mod p) &= \sum_{(x_2,\ldots,x_k)\in \!{F_p^{k-1}}} {\Pr}_{(x_2^'\cdots,x_k^')\in \!{F_p^{k-1}}}({x_2 = x_2^'},\ldots,{x_k = x_k^'})\cdot {\Pr}_{x_1\in \!F_p}(g_x(m)\equiv g_x(m')\mod p)\\
&= \sum_{(x_2,\ldots,x_k)\in \!{F_p^{k-1}}} \frac {1}{p^{k-1}} \cdot \frac {1}{p}\\
&=p^{k-1}\cdot \frac {1}{p^{k-1}} \cdot \frac {1}{p}\\
&=\frac {1}{p}
\end{align}

From the proof above, \frac{1}{p} is the collision probability of the attacker in 1 round, so on average p verification queries will suffice to get one message accepted. To reduce the collision probability, it is necessary to choose large p or to concatenate n such MACs using n independent keys so that the collision probability becomes \frac{1}{p^n}. In this case the number of keys are increased by a factor of n and the output is also increased by n.

MMH*32

Halevi and Krawczyk[4] construct a variant called MMH^*_{32}. The construction works with 32-bit integers and with the prime integer p=2^{32}+15. Actually the prime p can be chosen to be any prime which satisfies 2^{32}<p<2^{32}+2^{16}. This idea is adopted from the suggestion by Carter and Wegman to use the primes 2^{16}+1 or 2^{31}-1.

\mathrm{MMH}^*_{32} is defined as follows:
MMH^*_{32}=\big\{g_x (\big\{0,1\big\}^{32} )^k \big\} \to F_p,

where \big\{0,1\big\}^{32} means \big\{0, 1, \ldots, 2^{32}-1\big\} (i.e., binary representation)

The functions g_x are defined as follows.


\begin{align}
g_x (m)&\overset{\underset{\mathrm{def}}{}}{=} m \cdot x \mod (2^{32}+15)\\
&=\textstyle \sum_{i=1}^k m_i \cdot x_i \mod (2^{32}+15)
\end{align}

where

 x= (x_1,\ldots,x_k ), m=(m,\ldots,m_k )

By theorem 1, the collision probability is about ϵ = 2^{-32}, and the family of MMH^*_{32} can be defined as ϵ-almost ∆ Universal with ϵ = 2^{-32}.

The value of k

The value of k that describes the length of the message and key vectors has several effects:

Performance

Below are the timing results for various implementations of MMH[4] in 1997, designed by Halevi and Krawczyk.

150 MHz PowerPC 604 Message in Memory Message in Cache
64-bit 390 Mbit/second 417 Mbit/second
32-bit output 597 Mbit/second 820 Mbit/second
150 MHz PowerPC 604 Message in Memory Message in Cache
64-bit 296 Mbit/second 356 Mbit/second
32-bit output 556 Mbit/second 813 Mbit/second
150 MHz PowerPC 604 Message in Memory Message in Cache
64-bit 380 Mbit/second 500 Mbit/second
32-bit output 645 Mbit/second 1080 Mbit/second

See also

References

  1. 1 2 3 4 5 6 Boesgaard, Martin; Scavenius, Ove; Pedersen, Thomas; Christensen, Thomas; Zenner, Eric (2005). "Badger- A fast and provably secure MAC" (PDF).
  2. Lucks, Stefan; Rijmen, Vincent (2005). "Evaluation of Badger" (PDF).
  3. 1 2 3 "Badger Message Authentication Code,Algorithm Specification" (PDF). 2005.
  4. 1 2 3 Halevi, Shai; Krawczyk, Hugo (1997). "MMH:Software Message Authentication in the Gbit/second rates".
This article is issued from Wikipedia - version of the Saturday, April 23, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.