Test environment for supercop submissions
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
checksum
cpucycles
cpuid
crypto_aead
crypto_auth
crypto_box
crypto_core
crypto_dh
crypto_encrypt
crypto_hash
crypto_hashblocks
crypto_onetimeauth
crypto_scalarmult
crypto_secretbox
crypto_sign
crypto_stream
crypto_verify
cryptopp-562
gmp-6.0.0
include
inttypes
killafter
machineinfo
okcompilers-short
okcompilers
scripts
sinceepoch
OPERATIONS
README.md
data-do
data-init
data-run
data-summarize
data-unlock
data-vars
do
do-one-primitive
measure-anything.c
try-anything.c
try.h
trygen.do
trygen.py
version

README.md

supercop-fastbuild

This is supercop-20141010 with a few changes to make testing new primitives easier.

The main change is the addition of the "do-one-primitive" script. This lets you build just the packages you need to test the submission you're working on.

For instance, if you want to build pass769:

$ cd supercop-fastbuild
$ ./do-one-primitive crypto_core salsa20
$ ./do-one-primitive crypto_stream salsa20
$ ./do-one-primitive crypto_hash sha512
$ ./do-one-primitive crypto_sign pass769

(You may way to read ./bench/hostname/log or ./bench/hostname/work/errors after each call to do-one-primitive.)

I've also removed most of the compilers from okcompilers/{c,cpp} and told the compilers to produce debugging information by default.

Original source: http://hyperelliptic.org/ebats/supercop-20141010.tar.bz2

Supercop: http://bench.cr.yp.to/supercop.html