@@ -35,12 +35,21 @@ development shells provide static AWS-LC libraries.
3535First-party crypto selection lives in ` openshell-crypto ` : backend-neutral
3636primitive traits and protocol adapters preserve existing TLS, PKI, JWT, and
3737credential-storage behavior. Application crates enable integration features on
38- that crate instead of naming a backend. Process-default initialization preserves
39- existing embedder providers; context capability reporting does not attest those
40- globals or dependency-owned crypto. OpenSSL and strict FIPS operation are separate
41- follow-up work. The crate README defines extension and coverage boundaries.
38+ that crate instead of naming a backend. The workspace selects the default AWS-LC
39+ feature centrally. Backend-owned signing keys support fallible export and import;
40+ rcgen only adapts certificate encoding. Explicit context selection controls
41+ first-party TLS configuration even after Rustls global initialization. Without
42+ explicit selection, builders preserve embedder defaults. Capability reporting
43+ does not attest globals or dependency-owned crypto. This boundary prepares a
44+ system-OpenSSL backend; its proof of concept, dynamic-link packaging, and strict
45+ FIPS operation are separate follow-up work. The crate README defines extension and coverage boundaries.
4246Digest operations propagate backend failures through JWT and credential key-ID
4347generation rather than requiring infallible provider operations.
48+ Persisted CA metadata is parsed by ` openshell-crypto ` using ` x509-parser `
49+ without verification features. rcgen's parser feature remains disabled because
50+ it couples parsing to built-in CSR verification backends. Backend keys implement
51+ rcgen's signing trait directly; the proxy checks certificate/key matching through
52+ the selected TLS backend and retains the original CA bytes in certificate chains.
4453
4554SQLx uses AWS-LC with native certificate roots.
4655 The server enables
0 commit comments