aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus@rgdd.se>2023-03-23 13:23:57 +0100
committerRasmus Dahlberg <rasmus@rgdd.se>2023-03-23 13:24:02 +0100
commit85182f9a1007c46979a8f3be4acf165b27444d04 (patch)
treec58a075efb49e939d1cc42e304cd2cc56e2fc6ca
parent9023b4e3fe70ada7d466589e753e69d13573c157 (diff)
Editorial editsv0.0.2
-rw-r--r--README.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/README.md b/README.md
index f89fd7e..830c024 100644
--- a/README.md
+++ b/README.md
@@ -46,7 +46,7 @@ then download and verify the signatures of the logs' tree heads:
2023/03/23 12:43:59 cmd_snapshot.go:82: INFO: bootstrapped Trust Asia Log2023 at tree size 388349
2023/03/23 12:44:01 cmd_snapshot.go:82: INFO: bootstrapped Trust Asia Log2024-2 at tree size 112771
-Subsequent uses of the snapshot command will update the signed list of known
+Subsequent uses of the `snapshot` command will update the signed list of known
logs, then update the logs' signed tree heads after verifying consistency.
Download and verify the logs' Merkle trees up until the current snapshot:
@@ -74,14 +74,14 @@ Download and verify the logs' Merkle trees up until the current snapshot:
Trust Asia Log2024-2 | 246.2 entries/s | Estimated done in 0.11 hours | Working on [17664, 112771)
This will take a while depending on the local system, configuration of the
-optional `ct-sans collect` flags, as well as how heavily the logs apply
-rate-limits. For good performance while respecting rate-limits, you may want
-to try `--workers 40 --batch-disk 131072 --batch-req 2048 --metrics 60m`. This
-allowed us to download the logs (March 2023) in approximately 10 days. Our
-single-IP EU machine had a 2 TiB SSD, 64 GiB memory, 16 CPU cores, and 1 Gbps.
+optional `collect` flags, as well as how heavily the logs apply rate-limits.
+For good performance while respecting rate-limits, you may want to try
+`--workers 40 --batch-disk 131072 --batch-req 2048 --metrics 60m`. This allowed
+us to download the logs (March 2023) in approximately 10 days. Our machine was
+located in EU with 2TiB SSD, 64GiB memory, 16 CPU cores, and 1Gbps line-speed.
Of note is that it is safe to ctrl+C while collecting. Just wait for the
-collect command to exit on its own so that things are persisted to disk.
+`collect` command to exit on its own so that things are persisted to disk.
Once the collect phase is done, assemble the data set:
@@ -117,11 +117,11 @@ Once the collect phase is done, assemble the data set:
The SANs data set is sorted and de-duplicated, one SAN per line.
-**Note:** the different ct-sans commands must not run at the same time.
+**Note:** the different `ct-sans` commands must not run at the same time.
## Updating the data set
-Simply run the same snapshot, collect, and assemble commands again.
+Simply run the same `snapshot`, `collect`, and `assemble` commands again.
## Contact