21.03.2013 Views

Problem - Kevin Tafuro

Problem - Kevin Tafuro

Problem - Kevin Tafuro

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

See Also<br />

• NIST Cryptographic Module Validation Program home page: http://csrc.nist.gov/<br />

cryptval/<br />

• Recipe 11.2<br />

11.19 Performing Entropy Estimation and<br />

Management<br />

<strong>Problem</strong><br />

You are collecting your own entropy, and you need to determine when you have collected<br />

enough data to use the entropy.<br />

Solution<br />

At the highest level, the solution is to be incredibly conservative in entropy estimation.<br />

In the discussion, we will examine general practices and guidelines for particular<br />

sources.<br />

Discussion<br />

Fundamentally, the practical way to look at entropy is as a measurement of how<br />

much information in a piece of “random” data an attacker can glean about your randomness<br />

infrastructure. For example, if you have a trusted channel where you get<br />

128 bits of data, the question we are really asking is this: how much of that data is<br />

provided to an attacker through whatever data channels are available to him? The<br />

complexity of an attack is based on how much data an attacker has to guess.<br />

Clearly, in the practical sense, a single piece of data can have different amounts of<br />

entropy for different people. For example, suppose that we use the machine boot<br />

time to the nearest second as a source of entropy. An attacker who has information<br />

about the system startup time narrowing it down to the nearest week still has a much<br />

harder problem than an attacker who can narrow it down to a 10-second period. The<br />

second attacker can try all 10 possible starting values and see if he gets the correct<br />

value. The first has far, far more values to try before finding the original value.<br />

In practice, it turns out that boot time is often an even more horrible source of<br />

entropy than we have already suggested. The nmap tool can often give the system<br />

uptime of a remote host with little effort, although this depends on the operating system<br />

and the firewall configuration of the host being targeted.<br />

The basic lesson here is that, before you decide how to estimate entropy, you should<br />

figure out what your threat model is. That is, what kinds of attacks are you worried<br />

Performing Entropy Estimation and Management | 621<br />

This is the Title of the Book, eMatter Edition<br />

Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!