Accept file payloads for pipe send
This commit is contained in:
parent
78dbbf240b
commit
55cb455de3
5 changed files with 34 additions and 11 deletions
|
|
@ -177,8 +177,8 @@ Roadmap items should be actionable and checkable:
|
|||
ALPN and requires `pipe.connect` on `resource:pipe:<name>`. Remote
|
||||
`geth pipe listen <name> --node <node-id>` requires `pipe.listen` on the same
|
||||
resource before creating a daemon-lifetime listener on the peer. `geth pipe
|
||||
send <name> <message> --node <node-id>` carries a byte message over the
|
||||
dedicated `/geth/pipe/1` ALPN when `pipe.connect` is authorized, and
|
||||
send <name> [message|--in <path>|--in -] --node <node-id>` carries a byte
|
||||
message over the dedicated `/geth/pipe/1` ALPN when `pipe.connect` is authorized, and
|
||||
`geth pipe recv <name>` drains local daemon-lifetime messages. Long-lived
|
||||
bidirectional streams and TCP/Unix forwarding are still roadmap work.
|
||||
- `geth ssh proxy <node-id>` performs an authorized control-plane handshake over
|
||||
|
|
|
|||
Loading…
Reference in a new issue