Add authorized Unix pipe forwarding
This commit is contained in:
parent
6bc2666993
commit
3d0da22eae
8 changed files with 491 additions and 16 deletions
|
|
@ -183,8 +183,11 @@ Roadmap items should be actionable and checkable:
|
|||
forward-tcp --listen 127.0.0.1:<port> --node <node-id> --target
|
||||
127.0.0.1:<port>` opens authorized bidirectional byte streams over
|
||||
`/geth/pipe/1`; the remote daemon requires `pipe.forward` on
|
||||
`resource:pipe-tcp:<target>` before connecting to the loopback target. Unix
|
||||
socket forwarding is still roadmap work.
|
||||
`resource:pipe-tcp:<target>` before connecting to the loopback target. `geth
|
||||
pipe forward-unix --listen <local-socket> --node <node-id> --target
|
||||
<remote-socket>` uses the same Iroh path and requires `pipe.forward` on
|
||||
`resource:pipe-unix:<target>` before connecting to an absolute Unix socket
|
||||
path.
|
||||
- `geth ssh proxy <node-id>` is a streaming OpenSSH ProxyCommand-style path. The
|
||||
CLI streams through the local daemon, the daemon uses `/geth/ssh-proxy/1` over
|
||||
Iroh, the remote daemon requires `ssh_proxy.connect` on
|
||||
|
|
|
|||
Loading…
Reference in a new issue