Live data from Hacker News

Magic Wormhole: get things from one computer to another, safely

github.com

101–110 of 262 posts

Re: Magic Wormhole: get things from one computer to another, safely

#101

Earlier quoted context omitted.

(magic-wormhole author here) Thanks for making a donation! I run the relay server, but the Debian maintainer agreed to bake an alternate hostname into the packaged versions (a CNAME for the same address that the upstream git code uses), so we could change it easily if the cost ever got to be a burden. It hasn't been a problem so far, it moves 10-15 TB per month, but shares a bandwidth pool with other servers I'm rent…

Seems like the only way to ensure wormhole to scale is to only to use relay server to setup direct connections. I know this requires one of the ends to be able to open ports or whatever but that should be baked into the wormhole setup.

Maybe hole punching or similar might be worth examining?

Re: Magic Wormhole: get things from one computer to another, safely

#102

Earlier quoted context omitted.

(magic-wormhole author here) Thanks for making a donation! I run the relay server, but the Debian maintainer agreed to bake an alternate hostname into the packaged versions (a CNAME for the same address that the upstream git code uses), so we could change it easily if the cost ever got to be a burden. It hasn't been a problem so far, it moves 10-15 TB per month, but shares a bandwidth pool with other servers I'm rent…

> move to a slower-but-flat-rate provider As I'm sure you're aware: https://www.scaleway.com/en/stardust-instances/ "up to 100Mbps" for $4/month

Hetzner.de has 1 gbps unlimited or 10 gbps with a 20TB limit on their bare metal servers. And those can be bought very cheap if you don't need any special hardware.

Re: Magic Wormhole: get things from one computer to another, safely

#104
post #12

Earlier quoted context omitted.

And more https://github.com/mat-sz/filedrop https://github.com/saljam/webwormhole https://github.com/schollz/croc https://github.com/dutchcoders/transfer.sh https://github.com/timvisee/send https://github.com/schlagmichdoch/pairdrop https://github.com/SnapDrop/snapdrop

I have a list of now 22 browser based p2p sharing tools that i shared here a few times in similar threads https://gist.github.com/SMUsamaShah/fd6e275e44009b72f64d0570...

I find myself using Send Anywhere [1] all the time. I couldn't find documentation on how the files are transferred or if they're uploaded to their cloud, but it's very handy. They claim the files are encrypted in transmission, but don't give details & could just be talking about SSL.[2]

When you choose the files you want to transfer, it gives you a 6 digit code or a QR code. Once you enter that, the files are transferred! It's available for most all major platforms, but isn't open source. [3]

I haven't read their privacy policy. Frankly, I'd rather not know...

[1] https://send-anywhere.com/

[2] https://support.send-anywhere.com/hc/en-us/articles/11500385...

[3] https://support.send-anywhere.com/hc/en-us/articles/11500388...

Re: Magic Wormhole: get things from one computer to another, safely

#105
I wasn't yet planning for it, but what the heck.

https://zynk.it is a new project I've been working on together with a small team aimed at delivering a truly easy, fast, efficient, unlimited, privacy-respecting and pain free file-sharing experience. It’s peer-to-peer, E2EE and avoids centralized storage, aligning with the ethos of control and transparency we often discuss here. It allows users to send and receive any file(s) or folder(s) without any limits whatsoever between any device/OS and any device/OS, send and forget, Zynk takes care of all the heavy lifting.

What I hope sets Zynk apart is that it is built to literally be used by anyone, be it a power user, or my mom.

One of my main goals with this project is to remove any pains associated with data transfer once and for all, for any use case.

I'm curious if this resonates with you—would you use it? What would make it indispensable for your workflows?

I'd be happy to discuss it more if anyone is interested. Feel free to sign up for early access on the site.

Re: Magic Wormhole: get things from one computer to another, safely

#106

Earlier quoted context omitted.

Why is this better than rsycn or scp?

scp/rsync are great tools, but they require pre-coordination of keys. One side is the client, the other is the server. The client needs an account on the server machine (so the human on the client machine must provide an ssh pubkey to the human on the server machine, who must be root, and create a new account with `adduser`, and populate the ~/.ssh/authorized_keys file). And the client needs to know the server's corr…

But if you already have ssh set up for the target machine, is there any advantage such as speed or recoverability vs scp?

Re: Magic Wormhole: get things from one computer to another, safely

#107

I've used wormhole once to move a 70 GB file. Couldn't possibly do that before. And yes, I know I used the bandwidth of the relay server, I donated to Debian immediately afterwards (they run the relay for the version in the apt package).

The wormhole transit protocol will attempt to arrange a direct connection and avoid transferring data through the relay.

Is there a switch to fail rather than fall back on relay?

Re: Magic Wormhole: get things from one computer to another, safely

#108
post #55

Earlier quoted context omitted.

Right. Also you may have to reconfigure some firewalls to use scp. Typically, a firewall allows outbound connections without needing an explicit entry for the protocol, and in the case of magic wormhole, both sides are an outbound connection. So it passes right through. If you've got security-minded folk managing that sort of thing for you, it's possible that magic wormhole will upset them for this reason. More for p…

Both problems can be worked around by having a third, general-purpose host where both source/destination hosts can scp to/from. Not quite as straightforward because you have to copy twice and do it from both sides, but has the benefit of not having to install bespoke software.

I think you could use an ssh tunnel between the intermediary and the destination such that the scp connection from the source makes it all the way through in one go, rather than leaving files on the intermediary. You'd be forwarding to the ssh port via ssh, so it would be a confusing bit of sshception.

If I tried to actually come up with the actual commands for this, I'm sure I'd burn a whole afternoon on fiddling with it.

Post reply on HN