docs: unwrap hand-wrapped prose repo-wide
Gates / frontend (push) Successful in 1m2s
Gates / test (push) Successful in 1m38s
Gates / package (push) Successful in 5m5s
Gates / test-aarch64 (push) Successful in 6m30s
Gates / container (push) Successful in 15s
CI / gates (push) Successful in 13m30s

This commit is contained in:
2026-08-15 16:27:36 +02:00
parent 50b8fd5c61
commit 5b3d1cd65c
48 changed files with 2691 additions and 11699 deletions
+4 -14
View File
@@ -1,9 +1,6 @@
# Test fixtures
`self_signed_cert.pem`/`self_signed_key.pem` and
`self_signed_cert2.pem`/`self_signed_key2.pem` are **test fixtures**. The
private keys are **intentionally committed** to this public repository. They
are not secrets and must never protect anything real.
`self_signed_cert.pem`/`self_signed_key.pem` and `self_signed_cert2.pem`/`self_signed_key2.pem` are **test fixtures**. The private keys are **intentionally committed** to this public repository. They are not secrets and must never protect anything real.
Properties:
@@ -12,10 +9,7 @@ Properties:
- SAN `DNS:localhost`, `IP:127.0.0.1`
- Validity 36500 days from generation
The loopback TLS test in `src/platform/tls_server.zig` uses the first pair.
The second pair exists so certificate-reload tests can swap between two valid
identities (milestone-10 ruling 13). Nothing in the shipped binary reads
either.
The loopback TLS test in `src/platform/tls_server.zig` uses the first pair. The second pair exists so certificate-reload tests can swap between two valid identities (milestone-10 ruling 13). Nothing in the shipped binary reads either.
Regenerate with (substitute `2` in both file names for the second pair):
@@ -26,9 +20,7 @@ openssl req -new -x509 -key self_signed_key.pem -out self_signed_cert.pem \
-addext "subjectAltName=DNS:localhost,IP:127.0.0.1"
```
`mismatched_key.pem` is a second EC P-256 key with no certificate. It parses,
but it does not belong to `self_signed_cert.pem`, so `ServerContext.init` must
reject the pair with `error.KeyMismatch`. It is not a secret either.
`mismatched_key.pem` is a second EC P-256 key with no certificate. It parses, but it does not belong to `self_signed_cert.pem`, so `ServerContext.init` must reject the pair with `error.KeyMismatch`. It is not a secret either.
Regenerate with:
@@ -36,6 +28,4 @@ Regenerate with:
openssl ecparam -name prime256v1 -genkey -noout -out mismatched_key.pem
```
`container-smoke.zon` is the smallest configuration that lets the daemon reach
`serving`. `tools/container_check.zig` copies it into the smoke container, which
is the only thing that reads it.
`container-smoke.zon` is the smallest configuration that lets the daemon reach `serving`. `tools/container_check.zig` copies it into the smoke container, which is the only thing that reads it.