No description
  • HTML 67.6%
  • Dockerfile 25.7%
  • HCL 3.1%
  • Makefile 3%
  • Procfile 0.6%
Find a file
2026-08-08 04:39:06 -04:00
caution.hcl update to steve 2.0 2026-08-08 04:39:06 -04:00
Containerfile update to steve 2.0 2026-08-08 04:39:06 -04:00
index.html initial commit 2025-12-23 10:07:59 -08:00
LICENSE initial commit 2025-12-23 10:07:59 -08:00
Makefile initial commit 2025-12-23 10:07:59 -08:00
Procfile add back source 2025-12-26 14:37:12 -08:00
README.md initial commit 2025-12-23 10:07:59 -08:00

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 param
  • GET /health - Health check: {"status": "ok"}