The ACME client MUST take the issue of a certificate from the library net (@intellectual-frontiers/net, net 0001-netFR-008), where it is specified and proved (0032-libraries-by-concernFR-010), and MUST NOT specify it here.
Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library net: 0001-net FR-008
The ACME client MUST take the signed requests from the library net (@intellectual-frontiers/net, net 0001-netFR-009), where it is specified and proved (0032-libraries-by-concernFR-010), and MUST NOT specify it here.
Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library net: 0001-net FR-009
The ACME client MUST take the account from the library net (@intellectual-frontiers/net, net 0001-netFR-010), where it is specified and proved (0032-libraries-by-concernFR-010), and MUST NOT specify it here.
Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library net: 0001-net FR-010
The ACME client MUST take the removal of the TXT records from the library net (@intellectual-frontiers/net, net 0001-netFR-011), where it is specified and proved (0032-libraries-by-concernFR-010), and MUST NOT specify it here.
Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library net: 0001-net FR-011
The ACME client MUST take the failures as Results from the library net (@intellectual-frontiers/net, net 0001-netFR-012), where it is specified and proved (0032-libraries-by-concernFR-010), and MUST NOT specify it here.
Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library net: 0001-net FR-012
The ACME client MUST take the certificate signing request from the library net (@intellectual-frontiers/net, net 0001-netFR-013), where it is specified and proved (0032-libraries-by-concernFR-010), and MUST NOT specify it here.
Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library net: 0001-net FR-013
The ACME client MUST take the validity of a certificate from the library net (@intellectual-frontiers/net, net 0001-netFR-014), where it is specified and proved (0032-libraries-by-concernFR-010), and MUST NOT specify it here.
Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library net: 0001-net FR-014
The ACME client MUST take the DNS host from the library net (@intellectual-frontiers/net, net 0001-netFR-015), where it is specified and proved (0032-libraries-by-concernFR-010), and MUST NOT specify it here.
Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library net: 0001-net FR-015
HTTP-01 and TLS-ALPN-01, External Account Binding, revocation, key rollover, account deactivation and ACME Renewal Information (RFC 9773): commons may add them when a harness needs one.
Keys other than ES256 for the account or the certificate.
Where a certificate and its keys are kept, and when a harness runs issue: the harness's (stolos), with the secret store it already has.
Waiting for a record to be seen by the DNS: the caller's propagationWait, which can ask the zone's own servers with runtime/dns.ts.
The CA follows RFC 8555 as Let's Encrypt does: Replay-Nonce on every response, Location for accounts and orders, problem documents of type urn:ietf:params:acme:error:*.
Web Crypto's ECDSA on P-256, its JWK, SPKI and PKCS #8 forms are in every runtime IFC TypeScript runs on.
A harness keeps the account key as a secret and gives it back to the next run; a lost key costs a new account and nothing else.
Tests use a fake CA and a fake Cloudflare and reach neither the real ones.