refactor: centralize peer control caller auth
This commit is contained in:
parent
f88bc851a4
commit
1a6d9db913
3 changed files with 153 additions and 384 deletions
|
|
@ -101,6 +101,11 @@ authenticates the Iroh endpoint and peer-card signature, but it does not
|
|||
authorize any resource module. Protected peer control requests must also prove
|
||||
that the signed peer card binds the observed Iroh EndpointID, then reduce
|
||||
resource auth ops; an EndpointID alone is not accepted as a resource principal.
|
||||
Inbound protected control, pipe-wire, SSH-proxy, and overlay-wire handlers use a
|
||||
shared authenticated caller context that validates the peer card, checks the
|
||||
observed endpoint binding, records the peer card as untrusted candidate
|
||||
metadata, and then passes the verified caller identity plus store handle to the
|
||||
resource-specific authorization step.
|
||||
Remote geth JSONL messages over Iroh are bounded before decoding:
|
||||
peer-control and module wire requests/responses are limited to 16 MiB,
|
||||
streaming handshakes for SSH proxy and TCP/Unix pipe forwarding are limited to
|
||||
|
|
|
|||
Loading…
Reference in a new issue