Stream SSH proxy over Iroh
This commit is contained in:
parent
55cb455de3
commit
87d8801d71
7 changed files with 366 additions and 23 deletions
|
|
@ -216,10 +216,14 @@ listener after the same endpoint/card and capability checks. `geth pipe recv
|
|||
checking `pipe.listen` on the same resource. Long-lived stdin/stdout streams and
|
||||
TCP/Unix forwarding are still future work.
|
||||
|
||||
`geth-ssh-proxy` currently defines proxy target and connection metadata. The
|
||||
daemon can authorize a remote proxy attempt over the protected Iroh control ALPN
|
||||
with `ssh_proxy.connect` on `resource:ssh-proxy:local`, but it does not yet
|
||||
forward bytes or connect to sshd/admin shell.
|
||||
`geth-ssh-proxy` defines proxy target and connection metadata. `geth ssh proxy
|
||||
<node>` is a streaming command intended for OpenSSH `ProxyCommand`: the CLI
|
||||
streams stdin/stdout through the local daemon, the local daemon dials the remote
|
||||
daemon with `/geth/ssh-proxy/1`, the remote daemon validates the signed peer card
|
||||
against the observed Iroh EndpointID, reduces `ssh_proxy.connect` on
|
||||
`resource:ssh-proxy:local`, and only then connects the Iroh stream to
|
||||
`127.0.0.1:22`. OpenSSH still performs its normal login authentication over the
|
||||
resulting byte stream. SSH is not used as a geth transport backend.
|
||||
|
||||
`geth-ssh-identity` defines SSH trust namespaces plus certificate request,
|
||||
approval, certificate import, and revocation-list data models. The bootstrap
|
||||
|
|
|
|||
Loading…
Reference in a new issue