Contributions welcome.
| Service | CLI? | Max Size | Direct Access | Files Expire? | Can Limit Download Count? | Password Protection | HTTPS |
|---|---|---|---|---|---|---|---|
| c-v.sh | curl -F |
4 GB | Yes | Yes, by Mister Alg. | No | No | Enforced |
| FileIO | Yes | 5 GB | Yes | Optionally | Fixed @ 1 | No | Yes |
| 0x0.st | Yes | 512MiB | Yes | Yes | No | No | Yes |
| Instant | No | UL | No | When seeders die | No | No | Enforced |
| ki.tc | Yes | 100mb | Yes | Upon Access | Singular | No | No |
| uguu.se | Yes | 100mb | Yes | 1 Day | No | No | Yes |
| oshi.at | Yes | 1 GB | Yes | Yes | Yes | No | Yes |
| Flyle | Yes - FFSend | 2.5 GB | no | Yes | Yes | Yes | Enforced |
It's a good idea to encrypt your files locally before sending them out, even if you trust the service. Here's a short how-to.
Encrypt with 256 bit AES:
openssl enc -aes-256-cbc -salt -in <infile> -out <outfile>
Decrypt:
openssl enc -aes-256-cbc -d -in <infile> -out <outfile>
Skip the -in and -out options to make openssl use STDIN or STDOUT.
See man enc for information on available ciphers. aes-256-cbc and bf are
what I generally use.
- u/86rd9t7ofy8pguh's analyzed the state of https on some of these sites here.