Live data from Hacker News

$ cat ~/myfile | curl -X PUT --upload-file “-” https://transfer.sh/myfile.txt

transfer.sh

1–10 of 125 posts

Re: $ cat ~/myfile | curl -X PUT --upload-file “-” https://transfer.sh/myfile.txt

#6
post #2

Neat idea, and props for the https. Are the files encrypted on the server?

There's an example on how to encrypt the files before sending them to the server:

  # Encrypt files with password using gpg 
  $ cat /tmp/hello.txt|gpg -ac -o-|curl -X PUT --upload-file "-" https://transfer.sh/test.txt 
  
  # Download and decrypt 
  $ curl https://transfer.sh/1lDau/test.txt|gpg -o- > /tmp/hello.txt

Re: $ cat ~/myfile | curl -X PUT --upload-file “-” https://transfer.sh/myfile.txt

#8
post #2

Neat idea, and props for the https. Are the files encrypted on the server?

It doesn't appear so, no. The raw bytes seem to be dumped to temp files, local storage, or S3 [1][2] without mention of any sort of encryption step (or reading of a secret somewhere). As mentioned below, you could encrypt before uploading of course. Someone please correct me if I misread though.

[1] https://github.com/dutchcoders/transfer.sh/blob/master/trans...

[2] https://github.com/dutchcoders/transfer.sh/blob/master/trans...

Re: $ cat ~/myfile | curl -X PUT --upload-file “-” https://transfer.sh/myfile.txt

#10
post #7

What's the advantage of doing this instead of just using SCP or SFTP?

With SFTP and SCP you need to run a daemon on the hosting machine, and create credentials for the other user to login so it's a bunch of extra steps.

For a lot of people with firewalls and no root / admin access, it becomes a major pain.

Post reply on HN