Connect pipes over Iroh control
This commit is contained in:
parent
e294965833
commit
741bd202a8
8 changed files with 344 additions and 32 deletions
|
|
@ -150,9 +150,10 @@ Roadmap items should be actionable and checkable:
|
|||
bounded in-memory ring buffer. Remote publish over the protected Iroh control
|
||||
ALPN requires `pubsub.publish` on `resource:pubsub:<topic>`. Iroh-gossip
|
||||
replication, private topics, and remote subscribe are still roadmap work.
|
||||
- Pipe listen/connect supports a local daemon-lifetime registry only. Iroh byte
|
||||
streams, TCP/Unix forwarding, and pipe capability enforcement are still
|
||||
roadmap work.
|
||||
- Pipe listen/connect supports a daemon-lifetime registry. Remote
|
||||
`geth pipe connect <name> --node <node-id>` uses the protected Iroh control
|
||||
ALPN and requires `pipe.connect` on `resource:pipe:<name>`. Iroh byte streams,
|
||||
TCP/Unix forwarding, and remote listener creation are still roadmap work.
|
||||
- Resource secret epoch metadata can be created, rotated, and listed locally.
|
||||
Bearer access metadata can be created/listed/revoked as resource-scoped auth
|
||||
ops and must not allow trust graph mutation capabilities. Payload encryption,
|
||||
|
|
|
|||
Loading…
Reference in a new issue