Okay. The equivalents to steps 1-11 were done by the Wormhole authors when they created the rendezvous server. So yes, if you use Wormhole in SaaS mode, it's s

Okay. The equivalents to steps 1-11 were done by the Wormhole authors when they created the rendezvous server. So yes, if you use Wormhole in SaaS mode, it's simpler, but you have to trust the rendezvous server. Operating scp with a working ssh server is as simple as working with wormhole: To push: scp foobar.txt tmp@www.example.com: #equivalent to wormhole send To pull: scp tmp@www.example.com:foobar.txt . #equivalent to wormhole receive To revoke access, you simply change the password, instead of deleting the user account. In fact, the steps you mention are what I already have by default on most of my machines, so there's 0% extra effort. I got rssh working in five minutes. Steps 10/11 are my responsibility, and the only remaining step for the other developer is step 7. Compare explaining the above two commands to explaining virtualenv and pip. On a busy public IRC channel, I'm not going to do that, I'll use scp, since it's also preinstalled on their system. So yes, I do rejoice in the simplicity. I commented for the benefit of those already running ssh, and who wondered how to create a similar setup to wormhole with what they have. rssh will work fine.