No description
- HTML 67.6%
- Dockerfile 25.7%
- HCL 3.1%
- Makefile 3%
- Procfile 0.6%
| caution.hcl | ||
| Containerfile | ||
| index.html | ||
| LICENSE | ||
| Makefile | ||
| Procfile | ||
| README.md | ||
Demo: Echo App
WARNING: This is not production ready software
A simple echo server demonstrating end-to-end encrypted communication with a Nitro Enclave.
End-to-End Encryption
All traffic is encrypted in the browser via a service worker before leaving, and only decrypted inside the enclave. The TLS gateway (Caddy) cannot read the encrypted payloads.
- Browser: Service worker encrypts requests (AES-256-GCM)
- Gateway: Caddy terminates TLS, forwards encrypted payload
- Enclave: Steve decrypts, forwards to app, encrypts response
Session keys are established via X25519 ECDH, verified against the enclave's attestation document.
See steve for implementation details.
Endpoints
POST /echo- Echo back JSON body:{"message": "hello"}→{"echo": "hello", "length": 5}GET /echo?message=hello- Echo back query paramGET /health- Health check:{"status": "ok"}