Randomness Testing Toolkit
Randomness testing toolkit (RTT) is a tool that unites execution of various statistical batteries used for testing that random data generated are without significant defects. It aims to detect non-randomness in given binary data in simple, automated manner while providing support for both small-scale testing and massive high-speed testing. RTT also post-processes outputs of batteries so one does not need to cope vith various output formats these batteries use.
RTT currently implements support for the following statistical tools:
- NIST Statistical Test Suite home page
- Dieharder: A Random Number Test Suite home page
- TestU01 home page
- BoolTest home page
This repository contains backend part of Randomness Testing Toolkit. For other parts see following repositories.
- Statistical batteries GitHub
Set of updated and modified statistical batteries compatible with RTT.
- Service deployment automation GitHub
RTT can be deployed on single or multiple servers as a service. Scripts in this repository automates the process of deployment.
- Web interface GitHub
The web interface is working on top of the deployed service and allow users to analyze data and view the analysis results through their browsers.
Installation and usage
For instructions on how to install and use Randomness Testing Toolkit, please refer to our wiki.
We run RTT for several years connected to high-speed computational resource called Metacentrum and used during various research activities. RTT is now very close to be dockerized for easy deployment locally if you want to just interactively upload one file for analysis.
The framework is developed at the Centre for Research on Cryptography and Security (formerly Laboratory of Security and Applied Cryptography), Masaryk University, Brno, Czech Republic since 2015, with parts of randomness testing reaching well back to 2005.
Randomness Testing Toolkit is licenced under MIT Licence, Copyright (c) 2015-2017 Centre for Research on Cryptography and Security. For details on MIT Licence, see file LICENSE.
Third party libraries
Some sub-parts of the project have their own licencing conditions. The brief list of such sub-parts follows.