After #406 we'd get a single signature for a request, but this still means ~0.2ms spent per request for signing and verifying it. That's OK for forwarded requests, but for local (ttl=1) in-container requests nodes can establish a shared secret (session-alike mechanism) and then use lighter HMAC-based proof for request authenticity.
After #406 we'd get a single signature for a request, but this still means ~0.2ms spent per request for signing and verifying it. That's OK for forwarded requests, but for local (ttl=1) in-container requests nodes can establish a shared secret (session-alike mechanism) and then use lighter HMAC-based proof for request authenticity.