crypto-inventory 0.3.0 and the control-plane planner after the second run on a tree that is not ours (libsignal): BoringSSL, Noise hfs, libcrux Kyber, the libsignal Java/Node API; self-signed trust anchors are blocked, test code is LOW with its own scope
This commit is contained in:
1 parent
42b049ef04
commit
e453c0c42d
35 files changed
+675
-51
No files matched your search
@@ -84,8 +84,10 @@ docker run --rm -p 443:8443 \
|
||||
|
||||
The mounted private key must be readable by the container user (uid 1000), otherwise the gateway refuses to start
|
||||
with `cannot read KEY (EACCES)`. The OpenSSL version inside the image is printed on the `listening` line; the gateway
|
||||
refuses to start if it is older than 3.5. Not yet measured by us: a build of this image and the OpenSSL version it
|
||||
carries (the test suite runs the gateway directly on Node.js 24 with OpenSSL 3.5.5).
|
||||
refuses to start if it is older than 3.5. Measured on 2026-10-18 from the committed bytes (`dovezi/imagine-docker-2026-10-18.md`):
|
||||
the image builds in 6 s (62.5 MB, `node:24-alpine`, runs as `node`), its base carries Node v24.22.0 with OpenSSL 3.5.8, a client
|
||||
offering only X25519MLKEM768 completes TLS 1.3 against it, a classical-only client is refused in `hybrid-only` and accepted in
|
||||
`hybrid-preferred` (where the hybrid group is chosen when offered). The test suite still runs the gateway directly on Node.js 24.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
Reference in new issue
Block a user