Ah right, but this does not support bidirectional streaming so I won't be able to get the remote stdout on the client, I guess.

▲ scottmf 6 days ago | parent [-]

Couldn’t you just pipe the stdout to another dumbpipe

▲ kwakubiney 6 days ago | parent [-]

Not a very friendly API

▲ scottmf 6 days ago | parent [-]

This works:

Remote:

  $ socat TCP-LISTEN:4321,reuseaddr,fork EXEC:"bash -li",pty,stderr,setsid,sigint,rawer&
  $ dumbpipe listen-tcp --host 127.0.0.1:4321
  using secret key fe82...7efd
  Forwarding incoming requests to '127.0.0.1:4321'.
  To connect, use e.g.:
  dumbpipe connect-tcp nodeabj...wkqay

Local:

  $ dumbpipe connect-tcp --addr 127.0.0.1:4321 nodeabj...wkqay&
  using secret key fe82...7efd
  $ nc 127.0.0.1 4321
  root@localhost:~#