aboutsummaryrefslogtreecommitdiffstats
path: root/checks/dolook2.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Allow test suite to build even if RNG or DLIES is missinglloyd2008-09-281-3/+14
|
* Clean up creation of RNG objectslloyd2008-09-151-9/+8
|
* New structure for entropy sources + RNGs. The entropy sources are owned bylloyd2008-06-271-11/+14
| | | | | | | Randpool, it will query them as needed (or if asked to do so). New function make_rng() that creates an RNG (X9.31 backed by a Randpool) and seeds it. Remove the entropy source related code from the Modules/Builtin_Modules classes.
* Remove uses of global PRNG from self-test and benchmark code. Assumeslloyd2008-06-271-1/+0
| | | | access to /dev/random (will be cleaned up shortly)
* Add a full set of tests for the ANSI X9.31 PRNG, using data takenlloyd2008-06-071-16/+36
| | | | | | | | from the NIST CAVS dataset, taken on June 7 2008 from http://csrc.nist.gov/groups/STM/cavp/standards.html AES-128, AES-192, AES-256, and 2 and 3-key TripleDES variants are all tested.
* Make the two parameters of Randpool (which underlying block cipher and MAClloyd2008-05-251-2/+3
| | | | to use) explicit arguments to the constructor instead of being hardcoded.
* Previously random_integer and friends used the global PRNG object to getlloyd2008-05-241-1/+1
| | | | | | | | | | | | | random bits. Now they take a reference to a RandomNumberGenerator object. This was applied several times out, so now the constructors to private key objects also take a RandomNumberGenerator& argument. This is also true for a number of randomized algorithms (Miller-Rabin, for instance). You can get a reference to the global PRNG with global_state().prng_reference() This is a provisional thing: and warning: it is not thread safe! If this is a problem instead keep per-thread PRNGs and pass them were needed.
* Remove the Global_RNG namespace, along with rng.h and rng.cpp. This waslloyd2008-04-071-2/+2
| | | | | | | | | essentially a facade for the RNG object living in the global library state. Rewrite all callers to directly invoke the global state object: this makes it more clear what functions are actually accessing mutable state outside of the normal reference graph (and thus, which functions will have to be altered in order to remove this dependency). Other facades remain in place for the configuration object and the memory allocator factory.
* Revert the change that renamed append() to push_back(). As pointed outlloyd2007-11-151-1/+1
| | | | | | by Joel Low on the mailing list, the STL container types have only a single version of push_back(), along with variations of insert() for handling range-based appending.
* Rename MemoryRegion::append to push_backlloyd2007-11-141-1/+1
| | | | Change all callers in the library and self-test code.
* Remove several uses of old style C casts in favor of C++98's static_cast and lloyd2007-10-191-1/+1
| | | | reinterpret_cast
* Remove the public domain notices from the self-test/benchmark code,lloyd2006-08-091-2/+0
| | | | because it turns out to be something of a legal minefield.
* Initial checkin1.5.6lloyd2006-05-181-0/+136