container-test-run-certificates
checks.aarch64-linux.certificates
· build #606
· raw
1additionally exposed symbols:2 ca, client, server,3 start_all, machines, driver, Machine, wait_for_signal4Starting ca5Starting client6Starting server7891011<<< NixOS Stage 2 >>>1213booting system configuration /nix/store/8vlfcgqrqvyw8dcqprna310f3p0yvkgf-nixos-system-ca-test14running activation script...15setting up /etc...162: host0@if3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100017 link/ether 42:06:76:42:a9:8d brd ff:ff:ff:ff:ff:ff link-netnsid 018setting up age secrets...19starting systemd...20systemd 260.2 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)21Detected virtualization systemd-nspawn.22Detected architecture arm64.23Detected first boot.24Initializing machine ID from container UUID.25Applying preset policy.26Populated /etc with preset unit settings.27Queued start job for default target Multi-User System.28293031<<< Welcome to NixOS test (aarch64) - console >>>32+ systemd-run /bin/sh -c '/nix/store/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo eec42fc7-a7fd-46ce-92e3-79b293bd4b4a'33Running as unit: run-p467-i4353014.service; invocation ID: e065c75001ff41a5b8afd3014fc184b734To attach to container ca run on the same machine that runs the test:35 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*eec42fc7-a7fd-46ce-92e3-79b293bd4b4a') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 3637To inject external network and continue test, run:38sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py eec42fc7-a7fd-46ce-92e3-79b293bd4b4a3940<<< NixOS Stage 2 >>>4142booting system configuration /nix/store/6ahbs930fxkb3g0il7kr9qvyv4rydgn3-nixos-system-client-test43running activation script...44setting up /etc...452: host0@if4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100046 link/ether 2a:42:35:28:b1:2f brd ff:ff:ff:ff:ff:ff link-netnsid 047setting up age secrets...48starting systemd...49systemd 260.2 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)50Detected virtualization systemd-nspawn.51Detected architecture arm64.52Detected first boot.53Initializing machine ID from container UUID.54Applying preset policy.55Populated /etc with preset unit settings.56Queued start job for default target Multi-User System.57585960<<< Welcome to NixOS test (aarch64) - console >>>61+ systemd-run /bin/sh -c '/nix/store/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo 1e23f46d-cf73-439a-a440-6f876ef14407'62Running as unit: run-p304-i4353017.service; invocation ID: 8cea2c4950484de18f0474ab88f2687063To attach to container client run on the same machine that runs the test:64 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*1e23f46d-cf73-439a-a440-6f876ef14407') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 6566To inject external network and continue test, run:67sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 1e23f46d-cf73-439a-a440-6f876ef144076869<<< NixOS Stage 2 >>>7071booting system configuration /nix/store/fc7ymkxc4zfskk993nbs4l1zz03q21cn-nixos-system-server-test72running activation script...73setting up /etc...742: host0@if5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100075 link/ether be:aa:dd:39:86:e7 brd ff:ff:ff:ff:ff:ff link-netnsid 076setting up age secrets...77starting systemd...78systemd 260.2 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)79Detected virtualization systemd-nspawn.80Detected architecture arm64.81Detected first boot.82Initializing machine ID from container UUID.83Applying preset policy.84Populated /etc with preset unit settings.85Queued start job for default target Multi-User System.86878889<<< Welcome to NixOS test (aarch64) - console >>>90+ systemd-run /bin/sh -c '/nix/store/wjm08iz4sdw5qgmx58dimv8ch7gbyyaj-coreutils-9.11/bin/sleep 999999999 && echo a044fdd4-57a0-4cb2-8f29-3e56b8ac469e'91Running as unit: run-p396-i4353021.service; invocation ID: 28f67c712bab44a6a4066394583b13f392To attach to container server run on the same machine that runs the test:93 sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*a044fdd4-57a0-4cb2-8f29-3e56b8ac469e') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash 9495To inject external network and continue test, run:96sudo /nix/store/akbq19lqha5w5h9hcchn309znqm94pq0-python3-3.13.15/bin/python3.13 /nix/store/qrxpb4s36qq6d4f5n5c5d78f1y3lvyhy-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py a044fdd4-57a0-4cb2-8f29-3e56b8ac469e97+ systemctl restart acme-order-renew-ca.foo.service98+ systemctl restart acme-test.foo.service99client: waiting for success: curl -v https://test.foo100+ curl -v https://test.foo101* Host test.foo:443 was resolved.102* IPv6: (none)103* IPv4: 192.168.1.3104* Trying 192.168.1.3:443...105* ALPN: curl offers h2,http/1.1106} [5 bytes data]107* TLSv1.3 (OUT), TLS handshake, Client hello (1):108} [1552 bytes data]109* SSL Trust Anchors:110* OpenSSL default paths (fallback)111{ [5 bytes data]112* TLSv1.3 (IN), TLS handshake, Server hello (2):113{ [1210 bytes data]114* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):115{ [1 bytes data]116* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):117{ [19 bytes data]118* TLSv1.3 (IN), TLS handshake, Certificate (11):119{ [1008 bytes data]120* TLSv1.3 (IN), TLS handshake, CERT verify (15):121{ [110 bytes data]122* TLSv1.3 (IN), TLS handshake, Finished (20):123{ [52 bytes data]124* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):125} [1 bytes data]126* TLSv1.3 (OUT), TLS handshake, Finished (20):127} [52 bytes data]128* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey129* ALPN: server accepted h2130* Server certificate:131* subject: CN=test.foo132* start date: Sep 8 10:09:12 2026 GMT133* expire date: Oct 8 10:09:12 2028 GMT134* issuer: CN=minica root ca 6c492b135* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384136* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384137* subjectAltName: "test.foo" matches cert's "test.foo"138* OpenSSL verify result: 13139* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)140* closing connection #0141curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)142More details here: https://curl.se/docs/sslcerts.html143144curl failed to verify the legitimacy of the server and therefore could not145establish a secure connection to it. To learn more about this situation and146how to fix it, please visit the webpage mentioned above.147+ curl -v https://test.foo148* Host test.foo:443 was resolved.149* IPv6: (none)150* IPv4: 192.168.1.3151* Trying 192.168.1.3:443...152* ALPN: curl offers h2,http/1.1153} [5 bytes data]154* TLSv1.3 (OUT), TLS handshake, Client hello (1):155} [1552 bytes data]156* SSL Trust Anchors:157* OpenSSL default paths (fallback)158{ [5 bytes data]159* TLSv1.3 (IN), TLS handshake, Server hello (2):160{ [1210 bytes data]161* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):162{ [1 bytes data]163* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):164{ [19 bytes data]165* TLSv1.3 (IN), TLS handshake, Certificate (11):166{ [1008 bytes data]167* TLSv1.3 (IN), TLS handshake, CERT verify (15):168{ [111 bytes data]169* TLSv1.3 (IN), TLS handshake, Finished (20):170{ [52 bytes data]171* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):172} [1 bytes data]173* TLSv1.3 (OUT), TLS handshake, Finished (20):174} [52 bytes data]175* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey176* ALPN: server accepted h2177* Server certificate:178* subject: CN=test.foo179* start date: Sep 8 10:09:12 2026 GMT180* expire date: Oct 8 10:09:12 2028 GMT181* issuer: CN=minica root ca 6c492b182* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384183* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384184* subjectAltName: "test.foo" matches cert's "test.foo"185* OpenSSL verify result: 13186* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)187* closing connection #0188curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)189More details here: https://curl.se/docs/sslcerts.html190191curl failed to verify the legitimacy of the server and therefore could not192establish a secure connection to it. To learn more about this situation and193how to fix it, please visit the webpage mentioned above.194+ curl -v https://test.foo195* Host test.foo:443 was resolved.196* IPv6: (none)197* IPv4: 192.168.1.3198* Trying 192.168.1.3:443...199* ALPN: curl offers h2,http/1.1200} [5 bytes data]201* TLSv1.3 (OUT), TLS handshake, Client hello (1):202} [1552 bytes data]203* SSL Trust Anchors:204* OpenSSL default paths (fallback)205{ [5 bytes data]206* TLSv1.3 (IN), TLS handshake, Server hello (2):207{ [1210 bytes data]208* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):209{ [1 bytes data]210* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):211{ [19 bytes data]212* TLSv1.3 (IN), TLS handshake, Certificate (11):213{ [1008 bytes data]214* TLSv1.3 (IN), TLS handshake, CERT verify (15):215{ [110 bytes data]216* TLSv1.3 (IN), TLS handshake, Finished (20):217{ [52 bytes data]218* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):219} [1 bytes data]220* TLSv1.3 (OUT), TLS handshake, Finished (20):221} [52 bytes data]222* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey223* ALPN: server accepted h2224* Server certificate:225* subject: CN=test.foo226* start date: Sep 8 10:09:12 2026 GMT227* expire date: Oct 8 10:09:12 2028 GMT228* issuer: CN=minica root ca 6c492b229* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384230* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384231* subjectAltName: "test.foo" matches cert's "test.foo"232* OpenSSL verify result: 13233* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)234* closing connection #0235curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)236More details here: https://curl.se/docs/sslcerts.html237238curl failed to verify the legitimacy of the server and therefore could not239establish a secure connection to it. To learn more about this situation and240how to fix it, please visit the webpage mentioned above.241+ curl -v https://test.foo242* Host test.foo:443 was resolved.243* IPv6: (none)244* IPv4: 192.168.1.3245* Trying 192.168.1.3:443...246* ALPN: curl offers h2,http/1.1247} [5 bytes data]248* TLSv1.3 (OUT), TLS handshake, Client hello (1):249} [1552 bytes data]250* SSL Trust Anchors:251* OpenSSL default paths (fallback)252{ [5 bytes data]253* TLSv1.3 (IN), TLS handshake, Server hello (2):254{ [1210 bytes data]255* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):256{ [1 bytes data]257* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):258{ [19 bytes data]259* TLSv1.3 (IN), TLS handshake, Certificate (11):260{ [1008 bytes data]261* TLSv1.3 (IN), TLS handshake, CERT verify (15):262{ [111 bytes data]263* TLSv1.3 (IN), TLS handshake, Finished (20):264{ [52 bytes data]265* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):266} [1 bytes data]267* TLSv1.3 (OUT), TLS handshake, Finished (20):268} [52 bytes data]269* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey270* ALPN: server accepted h2271* Server certificate:272* subject: CN=test.foo273* start date: Sep 8 10:09:12 2026 GMT274* expire date: Oct 8 10:09:12 2028 GMT275* issuer: CN=minica root ca 6c492b276* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384277* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384278* subjectAltName: "test.foo" matches cert's "test.foo"279* OpenSSL verify result: 13280* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)281* closing connection #0282curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)283More details here: https://curl.se/docs/sslcerts.html284285curl failed to verify the legitimacy of the server and therefore could not286establish a secure connection to it. To learn more about this situation and287how to fix it, please visit the webpage mentioned above.288+ curl -v https://test.foo289* Host test.foo:443 was resolved.290* IPv6: (none)291* IPv4: 192.168.1.3292* Trying 192.168.1.3:443...293* ALPN: curl offers h2,http/1.1294} [5 bytes data]295* TLSv1.3 (OUT), TLS handshake, Client hello (1):296} [1552 bytes data]297* SSL Trust Anchors:298* OpenSSL default paths (fallback)299{ [5 bytes data]300* TLSv1.3 (IN), TLS handshake, Server hello (2):301{ [1210 bytes data]302* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):303{ [1 bytes data]304* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):305{ [19 bytes data]306* TLSv1.3 (IN), TLS handshake, Certificate (11):307{ [1008 bytes data]308* TLSv1.3 (IN), TLS handshake, CERT verify (15):309{ [111 bytes data]310* TLSv1.3 (IN), TLS handshake, Finished (20):311{ [52 bytes data]312* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):313} [1 bytes data]314* TLSv1.3 (OUT), TLS handshake, Finished (20):315} [52 bytes data]316* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey317* ALPN: server accepted h2318* Server certificate:319* subject: CN=test.foo320* start date: Sep 8 10:09:12 2026 GMT321* expire date: Oct 8 10:09:12 2028 GMT322* issuer: CN=minica root ca 6c492b323* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384324* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384325* subjectAltName: "test.foo" matches cert's "test.foo"326* OpenSSL verify result: 13327* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)328* closing connection #0329curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)330More details here: https://curl.se/docs/sslcerts.html331332curl failed to verify the legitimacy of the server and therefore could not333establish a secure connection to it. To learn more about this situation and334how to fix it, please visit the webpage mentioned above.335+ curl -v https://test.foo336* Host test.foo:443 was resolved.337* IPv6: (none)338* IPv4: 192.168.1.3339* Trying 192.168.1.3:443...340* ALPN: curl offers h2,http/1.1341} [5 bytes data]342* TLSv1.3 (OUT), TLS handshake, Client hello (1):343} [1552 bytes data]344* SSL Trust Anchors:345* OpenSSL default paths (fallback)346{ [5 bytes data]347* TLSv1.3 (IN), TLS handshake, Server hello (2):348{ [1210 bytes data]349* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):350{ [1 bytes data]351* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):352{ [19 bytes data]353* TLSv1.3 (IN), TLS handshake, Certificate (11):354{ [1008 bytes data]355* TLSv1.3 (IN), TLS handshake, CERT verify (15):356{ [110 bytes data]357* TLSv1.3 (IN), TLS handshake, Finished (20):358{ [52 bytes data]359* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):360} [1 bytes data]361* TLSv1.3 (OUT), TLS handshake, Finished (20):362} [52 bytes data]363* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey364* ALPN: server accepted h2365* Server certificate:366* subject: CN=test.foo367* start date: Sep 8 10:09:12 2026 GMT368* expire date: Oct 8 10:09:12 2028 GMT369* issuer: CN=minica root ca 6c492b370* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384371* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384372* subjectAltName: "test.foo" matches cert's "test.foo"373* OpenSSL verify result: 13374* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)375* closing connection #0376curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)377More details here: https://curl.se/docs/sslcerts.html378379curl failed to verify the legitimacy of the server and therefore could not380establish a secure connection to it. To learn more about this situation and381how to fix it, please visit the webpage mentioned above.382+ curl -v https://test.foo383* Host test.foo:443 was resolved.384* IPv6: (none)385* IPv4: 192.168.1.3386* Trying 192.168.1.3:443...387* ALPN: curl offers h2,http/1.1388} [5 bytes data]389* TLSv1.3 (OUT), TLS handshake, Client hello (1):390} [1552 bytes data]391* SSL Trust Anchors:392* OpenSSL default paths (fallback)393{ [5 bytes data]394* TLSv1.3 (IN), TLS handshake, Server hello (2):395{ [1210 bytes data]396* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):397{ [1 bytes data]398* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):399{ [19 bytes data]400* TLSv1.3 (IN), TLS handshake, Certificate (11):401{ [1008 bytes data]402* TLSv1.3 (IN), TLS handshake, CERT verify (15):403{ [111 bytes data]404* TLSv1.3 (IN), TLS handshake, Finished (20):405{ [52 bytes data]406* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):407} [1 bytes data]408* TLSv1.3 (OUT), TLS handshake, Finished (20):409} [52 bytes data]410* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey411* ALPN: server accepted h2412* Server certificate:413* subject: CN=test.foo414* start date: Sep 8 10:09:12 2026 GMT415* expire date: Oct 8 10:09:12 2028 GMT416* issuer: CN=minica root ca 6c492b417* Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384418* Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384419* subjectAltName: "test.foo" matches cert's "test.foo"420* OpenSSL verify result: 13421* SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)422* closing connection #0423curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)424More details here: https://curl.se/docs/sslcerts.html425426curl failed to verify the legitimacy of the server and therefore could not427establish a secure connection to it. To learn more about this situation and428how to fix it, please visit the webpage mentioned above.429+ curl -v https://test.foo430* Host test.foo:443 was resolved.431* IPv6: (none)432* IPv4: 192.168.1.3433* Trying 192.168.1.3:443...434* ALPN: curl offers h2,http/1.1435} [5 bytes data]436* TLSv1.3 (OUT), TLS handshake, Client hello (1):437} [1552 bytes data]438* SSL Trust Anchors:439* OpenSSL default paths (fallback)440{ [5 bytes data]441* TLSv1.3 (IN), TLS handshake, Server hello (2):442{ [1210 bytes data]443* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):444{ [1 bytes data]445* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):446{ [19 bytes data]447* TLSv1.3 (IN), TLS handshake, Certificate (11):448{ [930 bytes data]449* TLSv1.3 (IN), TLS handshake, CERT verify (15):450{ [78 bytes data]451* TLSv1.3 (IN), TLS handshake, Finished (20):452{ [52 bytes data]453* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):454} [1 bytes data]455* TLSv1.3 (OUT), TLS handshake, Finished (20):456} [52 bytes data]457* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey458* ALPN: server accepted h2459* Server certificate:460* subject: CN=test.foo461* start date: Sep 8 10:08:29 2026 GMT462* expire date: Dec 7 10:09:29 2026 GMT463* issuer: CN=Clan Intermediate CA464* Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256465* Certificate level 1: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256466* Certificate level 2: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256467* subjectAltName: "test.foo" matches cert's "test.foo"468* OpenSSL verify result: 0469* SSL certificate verified via OpenSSL.470* Established connection to test.foo (192.168.1.3 port 443) from 192.168.1.2 port 49760 471 % Total % Received % Xferd Average Speed Time Time Time Current472 Dload Upload Total Spent Left Speed473 0 0 0 0 0 0 0 0 0* using HTTP/2474* [HTTP/2] [1] OPENED stream for https://test.foo/475* [HTTP/2] [1] [:method: GET]476* [HTTP/2] [1] [:scheme: https]477* [HTTP/2] [1] [:authority: test.foo]478* [HTTP/2] [1] [:path: /]479* [HTTP/2] [1] [user-agent: curl/8.21.0]480* [HTTP/2] [1] [accept: */*]481} [5 bytes data]482483484485486487* Request completely sent off488{ [5 bytes data]489* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):490{ [265 bytes data]491* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):492{ [265 bytes data]493494495496497498499500{ [5 bytes data]501100 20 100 20 0 0 826 0 0502* Connection #0 to host test.foo:443 left intact503(finished: waiting for success: curl -v https://test.foo, in 7.38 seconds)504+ openssl s_client -connect test.foo:443 -servername test.foo505+ openssl x509 -text -noout506Certificate:507 Data:508 Version: 3 (0x2)509 Serial Number:510 a5:62:8c:ad:b2:94:cc:5a:b6:1a:5e:c4:21:21:f0:52511 Signature Algorithm: ecdsa-with-SHA256512 Issuer: CN=Clan Intermediate CA513 Validity514 Not Before: Sep 8 10:08:29 2026 GMT515 Not After : Dec 7 10:09:29 2026 GMT516 Subject: CN=test.foo517 Subject Public Key Info:518 Public Key Algorithm: id-ecPublicKey519 Public-Key: (256 bit)520 pub:521 04:a0:e8:5d:0f:fe:20:ed:36:59:d3:8e:de:2c:08:522 dc:a7:5c:d5:4a:de:e2:66:bf:0a:aa:45:a3:fb:b4:523 54:2f:e7:e7:e9:ae:f9:ae:62:db:0b:62:c6:ad:b7:524 36:e7:8e:ea:c5:d5:65:c1:fd:9d:66:e4:de:cb:8f:525 15:17:e0:50:58526 ASN1 OID: prime256v1527 NIST CURVE: P-256528 X509v3 extensions:529 X509v3 Key Usage: critical530 Digital Signature531 X509v3 Extended Key Usage: 532 TLS Web Server Authentication, TLS Web Client Authentication533 X509v3 Subject Key Identifier: 534 47:26:FC:B3:A8:1F:E5:80:97:82:A0:CB:93:BB:33:E8:CE:1C:8A:AD535 X509v3 Authority Key Identifier: 536 A0:B8:49:96:08:35:4C:BC:4F:9C:54:F7:43:32:16:A5:F4:A4:45:C3537 X509v3 Subject Alternative Name: 538 DNS:test.foo539 1.3.6.1.4.1.37476.9000.64.1: 540 0......acme..541 Signature Algorithm: ecdsa-with-SHA256542 Signature Value:543 30:45:02:21:00:aa:66:46:f1:19:c6:f1:3b:86:28:f2:4f:ba:544 01:98:b8:4e:3c:fb:72:98:3b:3d:16:00:dc:f5:fe:42:d6:b3:545 a0:02:20:41:62:db:0e:ea:8f:d2:17:5f:80:6d:38:aa:40:fa:546 ec:97:27:fa:86:a4:98:f2:4b:9e:d6:c9:13:f9:00:4a:d2547548549