2 ms·
I cut this back drastically from earlier drafts which talked more about how the verification service was deployed, but wanted to save at least one diagram with
by tptacek 3y ago
I cut this back drastically from earlier drafts which talked more about how the verification service was deployed, but wanted to save at least one diagram with a Muppet in it, and spaced on blanking out the mTLS/TLS thing. Long story short: we originally deployed the verifier on NATS, not with direct HTTP, and so TLS wasn't an option; we wrote a Go implementation of Noise. It's just HTTP now (but still Noise for now).
The signing interface is mTLS-like (client-authenticated) because you can't just let any component sign. But really any component can verify, so all you need is server authentication.
- ramchip 3y agoMakes sense. The Muppet was definitely needed. Thank you!