You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
||2 years ago|
|argon2i||2 years ago|
|doc||2 years ago|
|include||2 years ago|
|src||2 years ago|
|.gitignore||2 years ago|
|COPYING||2 years ago|
|Makefile||2 years ago|
|README||2 years ago|
|config.sh||2 years ago|
|configure||2 years ago|
mkproof is a small C program for generating proofs of work.
If mkproof is available as a package on your system, prefer to install that
rather than build it yourself.
mkproof depends only on a POSIX-like environment and a C99 compiler.
This will produce three executables: mkchallenge, mkproof, and checkproof.
The situation: Bob wants Alice to do something, but Alice isn't sure if Bob is a
1. Alice runs `mkchallenge` and sends the challenge to Bob.
2. Bob runs `mkproof ` and wastes some CPU time. After several
minutes of work, a proof is printed to stdout.
3. Bob sends the proof to Alice.
4. Alice runs `checkproof ` to verify the work.
Now Alice can be reasonably confident that Bob is not a robot, and proceed with
To make a challenge, generate 16 random bytes. Choose the argon2 iterations and
memory parameters, and the number of zeroed digits, to tune the difficulty. The
challenge string is the terms "argon2id"; the iterations, memory use, and number
of digits which shall be zero, as decimal integers; and the random bytes as
hexadecimal; joining the terms with ":".
To make a proof, split the challenge by ":" and verify that the first token is
"argon2id". Decode the iterations, memory, and digits parameters, and the
Repeat the following algorithm to generate proofs until an argon2id key
is found whose first N bits are zero, where N is equal to the digits
1. Generate 16 random bytes (password).
2. Run argon2id with the generated password, and the memory and iteration
parameters provided by the challenge, and the challenge bytes as the salt.
The hash length and parallelism parameters shall be respectively set to 32
3. Encode the argon2id hash as hexadecimal.
When a suitable hash is found, encode the password in hexadecimal. This is the
proof which should be transmitted to the challenger.
To verify the proof, simply run the proof algorithm with the original challenge
parameters and the challengee's provided password and verify that the resulting
hexadecimal string is prefixed with the appropriate number of zeroes.
The defaults are tuned to take about five minutes on one core of a modern