additionally exposed symbols: ca, client, server, start_all, machines, driver, Machine, wait_for_signal Starting ca Starting client Starting server <<< NixOS Stage 2 >>> booting system configuration /nix/store/i2zfn72hy9wgc25js69cxiqwnhx9cds1-nixos-system-ca-test running activation script... setting up /etc... 2: host0@if3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:06:76:42:a9:8d brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 261.1 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/p79fmimbb698sv4c135kbdwlhjcqpd3p-coreutils-9.11/bin/sleep 999999999 && echo 4ad5dd22-1522-41ce-8903-72baf0b4d5f1' Running as unit: run-p471-i76149224.service; invocation ID: ad1066d075f7452abf627527e3ffdb70 To attach to container ca run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*4ad5dd22-1522-41ce-8903-72baf0b4d5f1') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/41m77i1296n33p6liin8ynr6wh3h6b7m-python3-3.14.6/bin/python3.14 /nix/store/5kaq06rm8h6acj0ggm4f0dswwr131zib-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py 4ad5dd22-1522-41ce-8903-72baf0b4d5f1 <<< NixOS Stage 2 >>> booting system configuration /nix/store/jzfbrinay7dg431g73di01df41qhivw6-nixos-system-client-test running activation script... setting up /etc... 2: host0@if5: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 2a:42:35:28:b1:2f brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 261.1 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/p79fmimbb698sv4c135kbdwlhjcqpd3p-coreutils-9.11/bin/sleep 999999999 && echo 1f9694d1-8ba7-4737-bd5c-04420e14bca2' Running as unit: run-p305-i76149227.service; invocation ID: 75eec67dc5854a468fc2deaffa319b2f To attach to container client run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*1f9694d1-8ba7-4737-bd5c-04420e14bca2') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/41m77i1296n33p6liin8ynr6wh3h6b7m-python3-3.14.6/bin/python3.14 /nix/store/5kaq06rm8h6acj0ggm4f0dswwr131zib-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py 1f9694d1-8ba7-4737-bd5c-04420e14bca2 <<< NixOS Stage 2 >>> booting system configuration /nix/store/ahr3ngaigchqpzd4xs65jlzc6vvh2zlv-nixos-system-server-test running activation script... setting up /etc... 2: host0@if4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether be:aa:dd:39:86:e7 brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 261.1 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/p79fmimbb698sv4c135kbdwlhjcqpd3p-coreutils-9.11/bin/sleep 999999999 && echo a3288b3c-457c-4849-9c48-be4f39a81752' Running as unit: run-p398-i76149253.service; invocation ID: 74a940c8b0aa48eb927db4d205e098c5 To attach to container server run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*a3288b3c-457c-4849-9c48-be4f39a81752') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/41m77i1296n33p6liin8ynr6wh3h6b7m-python3-3.14.6/bin/python3.14 /nix/store/5kaq06rm8h6acj0ggm4f0dswwr131zib-test-driver-0.0.1/lib/python3.14/site-packages/test_driver/inject_network.py a3288b3c-457c-4849-9c48-be4f39a81752 + systemctl restart acme-order-renew-ca.foo.service + systemctl restart acme-test.foo.service client: waiting for success: curl -v https://test.foo + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [1007 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [111 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Aug 5 05:05:16 2026 GMT * expire date: Sep 4 05:05:16 2028 GMT * issuer: CN=minica root ca 08a61a * Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 13 * SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) * closing connection #0 curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the webpage mentioned above. + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [1007 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [112 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Aug 5 05:05:16 2026 GMT * expire date: Sep 4 05:05:16 2028 GMT * issuer: CN=minica root ca 08a61a * Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 13 * SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) * closing connection #0 curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the webpage mentioned above. + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [1007 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [111 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Aug 5 05:05:16 2026 GMT * expire date: Sep 4 05:05:16 2028 GMT * issuer: CN=minica root ca 08a61a * Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 13 * SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) * closing connection #0 curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the webpage mentioned above. + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [1007 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [110 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Aug 5 05:05:16 2026 GMT * expire date: Sep 4 05:05:16 2028 GMT * issuer: CN=minica root ca 08a61a * Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 13 * SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) * closing connection #0 curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the webpage mentioned above. + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [931 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [79 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Aug 5 05:04:29 2026 GMT * expire date: Nov 3 05:05:29 2026 GMT * issuer: CN=Clan Intermediate CA * Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256 * Certificate level 1: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256 * Certificate level 2: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 0 * SSL certificate verified via OpenSSL. * Established connection to test.foo (192.168.1.3 port 443) from 192.168.1.2 port 51620 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 0* using HTTP/2 * [HTTP/2] [1] OPENED stream for https://test.foo/ * [HTTP/2] [1] [:method: GET] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: test.foo] * [HTTP/2] [1] [:path: /] * [HTTP/2] [1] [user-agent: curl/8.21.0] * [HTTP/2] [1] [accept: */*] } [5 bytes data] * Request completely sent off { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): { [265 bytes data] * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): { [265 bytes data] { [5 bytes data] 100 20 100 20 0 0 846 0 0 * Connection #0 to host test.foo:443 left intact (finished: waiting for success: curl -v https://test.foo, in 4.22 seconds) + openssl s_client -connect test.foo:443 -servername test.foo + openssl x509 -text -noout Certificate: Data: Version: 3 (0x2) Serial Number: 1f:71:d0:bf:37:16:68:8c:06:33:08:70:5d:cc:61:79 Signature Algorithm: ecdsa-with-SHA256 Issuer: CN=Clan Intermediate CA Validity Not Before: Aug 5 05:04:29 2026 GMT Not After : Nov 3 05:05:29 2026 GMT Subject: CN=test.foo Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (256 bit) pub: 04:0a:17:85:df:22:e4:07:c0:49:9e:d9:69:71:37: e5:06:89:5b:d3:a2:72:e3:30:a1:ad:e2:8b:d3:cc: 5b:44:81:77:5d:80:02:ef:c7:70:bf:83:44:fe:2e: 5d:ce:1e:69:00:29:04:df:ec:f4:bf:09:2d:f1:a3: 3a:6d:f1:60:94 ASN1 OID: prime256v1 NIST CURVE: P-256 X509v3 extensions: X509v3 Key Usage: critical Digital Signature X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Subject Key Identifier: 14:E2:44:9D:1E:2E:C6:BE:DB:A5:87:0C:89:F0:04:0F:C0:73:C8:5C X509v3 Authority Key Identifier: 29:A1:14:20:1F:7B:F0:20:F9:F3:5C:4D:65:9E:F9:CF:4E:90:51:CE X509v3 Subject Alternative Name: DNS:test.foo 1.3.6.1.4.1.37476.9000.64.1: 0......acme.. Signature Algorithm: ecdsa-with-SHA256 Signature Value: 30:45:02:20:2b:c2:9c:f0:98:44:25:68:ed:e6:bc:ae:33:64: 69:b0:42:cd:84:98:f6:4b:3c:f2:24:1c:61:8f:7f:64:d8:bc: 02:21:00:94:ec:7e:f8:c7:66:8b:7c:7d:03:57:43:59:ce:02: b8:e9:dc:0b:83:2d:eb:23:4b:7a:b1:7f:6c:d1:be:4c:5e