Live data from Hacker News

Transfer.sh – Easy file sharing from the command line

transfer.sh

81–88 of 88 posts

Re: Transfer.sh – Easy file sharing from the command line

#81
i'd like something like transfer.sh but without uploading files to a server. just relay.

if i wanted to upload files, i could just do that on my own webserver.

what i am looking for is: download via browser sharing from commandline or browser shared file is availble as long as the share-process keeps running (ideally also) self-hosted relay servers

Re: Transfer.sh – Easy file sharing from the command line

#82
post #8

This is exactly the use case for Magic Wormhole, which is what the cool kids use to transfer files: https://github.com/magic-wormhole/magic-wormhole Magic Wormhole uses an end-to-end PAKE to create an encrypted transport between two points in the Internet, using a rendezvous server. It doesn't store files, which is almost never what you want; it's not a way to send a file and have 10 or 100 people download it. But it…

What stops someone from using up all the channel IDs on the rendezvous server. Also why no attempt at NAT traversal; instead relaying traffic through a transit server. It's almost as if the project's purpose is not so much to create superior file transfer but more just to showcase a use of SPAKE2.

> almost as if the project's purpose is not so much to create superior file transfer but more just to showcase a use of SPAKE2.

That's my feeling too. See my rant: https://news.ycombinator.com/item?id=24519895

Re: Transfer.sh – Easy file sharing from the command line

#83
post #82

Earlier quoted context omitted.

What stops someone from using up all the channel IDs on the rendezvous server. Also why no attempt at NAT traversal; instead relaying traffic through a transit server. It's almost as if the project's purpose is not so much to create superior file transfer but more just to showcase a use of SPAKE2.

> almost as if the project's purpose is not so much to create superior file transfer but more just to showcase a use of SPAKE2. That's my feeling too. See my rant: https://news.ycombinator.com/item?id=24519895

This rant is pretty silly. Nick Lamb's took the time to refute it on that thread; you should acknowledge that before continuing to cite your thread as if nobody had corrected you.

Re: Transfer.sh – Easy file sharing from the command line

#84
post #34

Earlier quoted context omitted.

I don't know anything about croc, I haven't looked carefully at it, and don't recommend it (or have any opinion on it). Lots of smart people have looked at Magic Wormhole, which is one of the things that makes it neat.

This is a great way to make sure there are no alternatives to Magic Wormhole. If this attitude was common in web browsers, we would only have one software of its kind in every category. No choice for users whatsoever.

This sounds like a slippery slope. No one is saying not to try anything else, they're saying to make sure and use stuff that is more likely to be safe. In the case of web browsers, we do only use like 4 or 5 out of thousands.

Re: Transfer.sh – Easy file sharing from the command line

#85
post #83
post #82

Earlier quoted context omitted.

> almost as if the project's purpose is not so much to create superior file transfer but more just to showcase a use of SPAKE2. That's my feeling too. See my rant: https://news.ycombinator.com/item?id=24519895

This rant is pretty silly. Nick Lamb's took the time to refute it on that thread; you should acknowledge that before continuing to cite your thread as if nobody had corrected you.

Who's Nick Lamb?

Anyway, the thead is very short, so if there were any corrections there, people can read them and make their own mind.

Re: Transfer.sh – Easy file sharing from the command line

#86
post #85
post #83

Earlier quoted context omitted.

This rant is pretty silly. Nick Lamb's took the time to refute it on that thread; you should acknowledge that before continuing to cite your thread as if nobody had corrected you.

Who's Nick Lamb? Anyway, the thead is very short, so if there were any corrections there, people can read them and make their own mind.

Sure, people should just read that whole thread. It doesn't sound like Magic Wormhole's authentication really clicked for you in the original rant.

Re: Transfer.sh – Easy file sharing from the command line

#87

Earlier quoted context omitted.

You don't need an account on the target system. Target PC opens a port and starts listening (outputting to file) Sending machine establishes a connection to the listening port, and starts copying the file. Example (hide a file transfer as DNS traffic) Listening computer: nc -l -u -p 53 > output.file Sending computer: cat original.file > nc -u [destination ip address] 53 In this case you'd be dumb not to encrypt the f…

Thanks! - Your 'sending' snippet should use | instead of >. - ports 1-1023 are privileged.

Oops, you're right about the pipe..

I thought that looked a bit wrong, but ignored my gut. Privileged port: I'm root anyway. =) I can't make it too easy on these kids.

Re: Transfer.sh – Easy file sharing from the command line

#88
post #5

This stores files for two weeks on a third-party server. What advantages for the intended use cases does transfer.sh have over netcat invented 26 years ago? I know some people who have used nc for those entire 26 years to xfer files point-to-point from the command line.

Not sure if your comment is just a re-hash of the now famous HN comment on the Dropbox Show HN ("Why can't you just use rsync/scp"), but netcat which is a unix utility shares basically nothing with transfer.sh which is a web based file sharing application. Comparing them is really apples-to-houses. Netcat has it's uses, but one of them is not guiding your friends and/or family through a terminal in order for them to…

What I asked about was the intended use cases, considering transfer.sh and nc. What you mentioned is not one of the many listed use cases. Most of them are to transfer a .txt file.
Post reply on HN