3 ms·
These remote pipes are a largely a pipe dream due to very agile crypto scene. It requires a bloated spec to describe policies and be interoperable standard nobo
by bvrmn 3y ago
These remote pipes are a largely a pipe dream due to very agile crypto scene. It requires a bloated spec to describe policies and be interoperable standard nobody would use. `command1 | ssh host process | command2` works perfectly fine.
- MisterTea 3y agoThey're a pipe dream because you're thinking in terms of Unix and ssh. On plan 9 you just use http://man.postnix.pw/9front/8/tlssrv http://man.postnix.pw/9front/8/tlssrv
- bvrmn 3y agoAnd what prevents to run stunnel on Linux? Is there a way to specify remote address or remote run to use TLS to wrap your application transparently in plan 9? Otherwise plan 9 on the same abstraction level.
- MisterTea 3y agoI'm not sure what you mean but running software remotely is accomplished via http://man.postnix.pw/9front/1/rcpu http://man.postnix.pw/9front/1/rcpu
- rakoo 3y agostunnel is the tired version of inter-machines communication. It's a basic, raw socket between two processes, and all layers above must be reinvented again and again. Plan 9 with its protocol 9p is the wired version of inter-machines communication. You don't just link two random processes, you have the possibility to interconnect two directory trees, and since most useful software works through a directory tree, this means two processes can be linked by importing another tree on another machine and doing everything locally. It's possible to write something like "echo UNSEEN | imap-search | imap-get-summary" and have actual IMAP stuff done on another machine, and you don't see any of it. It is also possible to use `rcpu` to do what ssh does, and even more: the remote machine has access to the local machine. So for instance you can edit files locally, and have a rcpu connection to run builds on another machine that picks it from your local workstation. No clunky sshfs, no failing NFS, ...