Add a bunch of links

authors.md

@@ -16,3 +16,5 @@ The kitchen of this FAEST is manned by, in alphabetical order:
 - [Christian Rechberger](https://www.iaik.tugraz.at/person/christian-rechberger/) (TU Graz)
 - [Lawrence Roy](https://ldr709.gitlab.io/) (Aarhus University)
 - [Peter Scholl](https://pascholl.github.io/) (Aarhus University)
+
+{% include_relative references.md %}

components.md

@@ -5,7 +5,9 @@ title: "Ingredients"
 
 Ingredients for the FAEST:
 
-- VOLE-in-the-Head
-- QuickSilver Zero-Knowledge Proof
-- AES Algorithm
+- [VOLE-in-the-Head][vith_crypto]
+- [QuickSilver Zero-Knowledge Proof][quicksilver]
+- [AES Algorithm][aes_spec]
 - a pinch of salt
+
+{% include_relative references.md %}

index.md

@@ -4,7 +4,7 @@ title: "Come and join the FAEST"
 ---
 
 FAEST is a digital signature algorithm designed to be secure against quantum computers.
-The security of FAEST is based on standard cryptographic hash functions (SHA3) and the AES cipher. 
+The security of FAEST is based on standard cryptographic hash functions (SHAKE) and the [AES][aes_spec] block cipher.
 
 ## Design philosophy
 
@@ -14,10 +14,12 @@ The Zero-Knowledge proof system used for FAEST is based on a new design called V
 
 ## Performance
 
-For 128 bit security, our optimized implementation of FAEST can sign or verify in 0.9 milliseconds (for signatures of size 6.5 kilobytes) or 8.1 milliseconds (for signatures of size 5 kilobytes). When using AES in Even-Mansour mode, signature size can be further reduced to 4.6 kilobytes.
+For 128 bit security, our optimized implementation of FAEST can sign or verify in 0.9 milliseconds (for signatures of size 6.5 kilobytes) or 8.1 milliseconds (for signatures of size 5 kilobytes). When using AES in Even-Mansour mode, signature size can be further reduced to 4.6 kilobytes. Here are the benchmarks for our [AVX2](/software.html) implementation.
 
 {% include_relative avx2-perf.md %}
 
 ## Contact
 
 If you want to contact us, please send an e-mail to [[email protected]](mailto://[email protected])
+
+{% include_relative references.md %}

references.md

@@ -0,0 +1,9 @@
+[aes_spec]: https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.197-upd1.pdf
+[faest_avx_impl]: https://github.com/faest-sign/faest-avx
+[faest_ref_impl]: https://github.com/faest-sign/faest-ref
+[quicksilver]: https://eprint.iacr.org/2021/076
+[submission_1]: /TODO.zip
+[spec_1_0]: /TODO.pdf
+[spec_1_1]: /TODO.pdf
+[vith_crypto]: https://eprint.iacr.org/2023/TODO
+[vith_crypto_impl]: https://github.com/lenerd/homcomzk

resources.md

@@ -3,10 +3,15 @@ layout: page
 title: "Recipes"
 ---
 
-Spec
+Specification:
 
-NIST submission
+- [v1.1][spec_1_1] covers the same protocol, but fixes some issues with the document.
+- [v1.0][spec_1_0] was included in our round 1 submission to NIST.
+
+NIST round 1 [submission][submission_1].
 
 Papers
 
-- Crypto paper
+- Our Crypto 2023 [paper][vith_crypto] on VOLE-in-the-head.
+
+{% include_relative references.md %}

software.md

@@ -3,14 +3,23 @@ layout: page
 title: "Dishes"
 ---
 
-Reference implementation in C
+The benchmark numbers below were collected on a consumer notebook with an AMD Ryzen 7 5800H processor, with a base clock speed of 3.2 GHz and 16 GB memory.
+Simultaneous Multi-Threading and Precision Boost were enabled.
+The computer was running Linux 6.1.30, and the implementations were compiled with GCC 12.2.1.
+
+C
+
+- Reference [implementation][faest_ref_impl].
 
 {% include_relative ref-perf.md %}
 
-AVX2 in C
+- x86-64 [implementation][faest_avx_impl] with AVX2, AES-NI, and other ISA extensions.
 
 {% include_relative avx2-perf.md %}
 
 Rust
 
-- (older version, uses different primitives and is incompatible with spec)
+- [Implementation][vith_crypto_impl] for our Crypto 2023 [paper][vith_crypto].
+  Note that this is for an older version of our protocol, which uses different primitives and is incompatible with the specification.
+
+{% include_relative references.md %}