Hash of the challenge file for verification:
e83607eb 942b3ac1 394dfb2a 36b465a0
3bcea042 a8bceafe 16daa05d 7dc143dd
d9c3e807 7490083b be2839ad 8be6bbdd
f1e90896 d14eab37 0ea33fd0 c0d3c11e
response was based on the hash:
e83607eb 942b3ac1 394dfb2a 36b465a0
3bcea042 a8bceafe 16daa05d 7dc143dd
d9c3e807 7490083b be2839ad 8be6bbdd
f1e90896 d14eab37 0ea33fd0 c0d3c11e
Hash of the response file for verification:
c22a8a27 15feadad 42217518 ecca2788
fb771d57 8aa1f8e0 cef98ef5 7e6565b8
bf5ab833 298417de 5cddff07 520231b2
54ddc9c2 72817bf2 aae0d4ec 584500dc
Blake2b hash of the new_challenge file for participant #14:
a85053ff 17c3c395 e4c6ede7 4fe7df4d
85e64700 bff1a066 c429a515 db5fbbb4
04958b99 9304c2ae b8b537d3 55a38651
9fb531f7 34e8bd17 eeb7c85c aab3501e
The above new_challenge file: https://ppot.blob.core.windows.net/public/challenge_0014
Kevin Lackner's attestation:
Date: Nov 10 2019
Location: Piedmont CA
Device:
A spare Ubuntu box, physically located in my office.
Files stored on an external drive.
Challenge:
$ b2sum challenge
e83607eb942b3ac1394dfb2a36b465a03bcea042a8bceafe16daa05d7dc143ddd9c3e8077490083bbe2839ad8be6bbddf1e90896d14eab370ea33fd0c0d3c11e challenge
Response:
$ b2sum response
c22a8a2715feadad42217518ecca2788fb771d578aa1f8e0cef98ef57e6565b8bf5ab833298417de5cddff07520231b254ddc9c272817bf2aae0d4ec584500dc response
Afterwards:
I securely erased the drive and used massive to upload the response.
Kevin Lacker
github.com/lacker
twitter.com/lacker