After reading the readme I’m confused what the advantage is over just regular piping. ‘’’ command-on-server1 | ssh user@server2 'command-on-server2' ‘’’
Maybe better to use something like magic wormhole? https://github.com/magic-wormhole/magic-wormhole
This seems very similar to ssh-j.com (open source: https://bitbucket.org/ValdikSS/dropbear-sshj)
Is "ssh.beam.camp" an example hostname, or an instance that you run?
@kdsme9 I think this is great and you've done a great work putting it together and sharing it with us for free.
Using the public key to match streams on both ends is super clever. I will start using this since it fills a need I have almost every day. I work with many small AWS instances and sometimes I just need to copy a small file or something to them without having to install a whole new OS like some short sighted people here are suggesting.
You also shipped your product, which is something only ~1% of developers actually do, so congrats.
Forget about the naysayers and thank you for creating this, it will make my work easier :).
Edit: Downvote me all you want, I still like this thing.
I have used https://pipe.pico.sh/ for this. pico.sh also has a bunch of other SSH-accessible services, e.g. pastes, and paid (or free if self-hosted) port tunneling.
I don't see any advantage over plain "-o 'ProxyJump box.in.the.middle'"? I guess this is supposed to buffer things? But then again, that's what "tail -f" is for…
More confused than anything else…
Huh? Why I cannot just ssh from machine 2 to machine 1 and just type `tail`?
This is a great way to send all of your files to the author of the utility / operator of the website.