101–110 of 117 posts
A reliable UDP with a rendezvous server would allow for much more scalable P2P transfer. Unfortunately, I haven't found one implemented like this...
I like it! But for me ssh already provides a simple and secure way to move files from one place or another.. tar -cf - ./files.txt ./orDir/ | ssh host "(cd /dest/dir; tar -xf -)" Given that ssh it so ubiquitous I think this will always be my go to.
I use netcat a lot with my friends, we don't even have to do the SSH dance. On the receiving end: nc -vll 0.0.0.0 12345 | pv | tar xv On the sending end: tar cv files... | pv | nc -N "destination IP" 12345 pv is a nice tool that just reports on the rate and number of bytes moving through the pipe, optional if you don't have it. Throw in gpg --symmetric + gpg --decrypt for good measure if you want to encrypt it on the…
Of course it's written in Go. It's amazing to see the language embraced that much for server side apps.
Static binaries are magic :)
Earlier quoted context omitted.
I use netcat a lot with my friends, we don't even have to do the SSH dance. On the receiving end: nc -vll 0.0.0.0 12345 | pv | tar xv On the sending end: tar cv files... | pv | nc -N "destination IP" 12345 pv is a nice tool that just reports on the rate and number of bytes moving through the pipe, optional if you don't have it. Throw in gpg --symmetric + gpg --decrypt for good measure if you want to encrypt it on the…
That throws your files over the wire with no encryption, signing, or integrity verification. It might well be fine for your use, but I don't think I'd ever be comfortable with it.
Earlier quoted context omitted.
Indeed yes, but files were hosted for 14 days.
I would be much more concerned about people using this site for the transfer of illegal material (such as child abuse imagery). That's something literally any file sharing/image hosting site has to deal with. The 14 day limit won't make a difference as people disseminating that type of material are likely used to having to move it around frequently.
Earlier quoted context omitted.
Could you give a full example of how this would work? Receiver and sender..
tar cf - src/ | ssh $host "tar -C /dest/dir -xf -"
No encryption necessary No integrity checks No resume support Just plain and as fast it could get..
I need to try the netcat version but I'm hoping someone could show me a concurrent version of it that is mad fast.
Earlier quoted context omitted.
Static binaries are magic :)
Could you please go into details like what's basic difference b/w static binaries and apps which use dynamic linking. What are the benefits of one over another? Something like grokking this concept for once and all :D
There are so many tools that can transfer files between two computers. I really like ones like this because you don't have to have SSH access or forward any ports to send a file from A to B. Its similar vein to other peer-to-peer utilities like zget [1], sharedrop [2], instant.io (webtorrent) [3], filepizza (webtorrent) [4], magic-wormhole [5], toss [6], dat [7], and many many others. During Hacktoberfest I also star…
Earlier quoted context omitted.
tar cf - src/ | ssh $host "tar -C /dest/dir -xf -"
Do you have any idea about a crazy fast way to transfer files between two machines on the internal network? No encryption necessary No integrity checks No resume support Just plain and as fast it could get.. I need to try the netcat version but I'm hoping someone could show me a concurrent version of it that is mad fast.
Earlier quoted context omitted.
That throws your files over the wire with no encryption, signing, or integrity verification. It might well be fine for your use, but I don't think I'd ever be comfortable with it.
Did you miss the part of my comment where I explained how to add encryption?