3 ms·

Can you explain further? As far as I can tell, there does not appear to be any better possible option given the requirements (usable from a browser, legally def

by RyanZAG 14y ago

Can you explain further? As far as I can tell, there does not appear to be any better possible option given the requirements (usable from a browser, legally defensible, anonymous usage with proxies, resistant to DCMA takedowns, etc)

venomsnake 14y ago
Well ... I had this idea few years back. I am no encryption specialist. 1. I will get as many backblaze pods as I can. 2. Client will mostly be the same with few differences - the encryption will be symmetrical (AES probably), with randomly generated key from high quality entropy. This key will never leave the client. File names will be encrypted too. It will be bundled with the file and uploaded in some blob For directories - they can be tared first before encrypted. So the only thing that I will see as a host is file size. 3. There will be some more keys that will be generated and uploaded - keep alive and kill switch. keep alive must be given on regular intervals or content expires. The kill key will delete the file on the server and as many of the logs as legally possible, end of story. 4. The server returns the unique url. 5. You get some text on your screen that will give 3 urls - kill url - keep alive url - decrypt key - safe download url (http://something/url http://something/url) will be asked by the page to give key. Decrypt will be on the client too. - unsafe download url (http://something/url#key)the http://something/url#key)the javascript will begin decryption immediately but if someone intercepts the url - he will have the key. 5. Premium accounts will be given on scratch cards or bought with bitcoins. Donations will be accepted anyway but won't give benefits. 6. .onion address for upload 7. Outgoing bandwidth - the speed of the downloads for all but premium accounts will be function of the donations received the previous day. 8. Everything will be open , and the community will be allowed to audit the systems. That is in general details.
- ricardobeat 14y ago
  Users won't be happy with 1kb/s uploads via Tor. If you're going trough that bottleneck, this offers no advantages over a a standard file-sharing service hosted at a .onion node.
- ricardobeat 14y ago
  And btw, that's basically what Dropbox (and mostly every other private file sharing service) does: files are encrypted using your password as the key.
  - dublinben 14y ago
    Even if that's true, Dropbox is still able to access your files at any time. If you don't control the key yourself, it might as well not be encrypted.

by RyanZAG 14y ago

venomsnake 14y ago

Well ... I had this idea few years back. I am no encryption specialist. 1. I will get as many backblaze pods as I can. 2. Client will mostly be the same with few differences - the encryption will be symmetrical (AES probably), with randomly generated key from high quality entropy. This key will never leave the client. File names will be encrypted too. It will be bundled with the file and uploaded in some blob For directories - they can be tared first before encrypted. So the only thing that I will see as a host is file size. 3. There will be some more keys that will be generated and uploaded - keep alive and kill switch. keep alive must be given on regular intervals or content expires. The kill key will delete the file on the server and as many of the logs as legally possible, end of story. 4. The server returns the unique url. 5. You get some text on your screen that will give 3 urls - kill url - keep alive url - decrypt key - safe download url (http://something/url http://something/url) will be asked by the page to give key. Decrypt will be on the client too. - unsafe download url (http://something/url#key)the http://something/url#key)the javascript will begin decryption immediately but if someone intercepts the url - he will have the key. 5. Premium accounts will be given on scratch cards or bought with bitcoins. Donations will be accepted anyway but won't give benefits. 6. .onion address for upload 7. Outgoing bandwidth - the speed of the downloads for all but premium accounts will be function of the donations received the previous day. 8. Everything will be open , and the community will be allowed to audit the systems. That is in general details.

ricardobeat 14y ago
Users won't be happy with 1kb/s uploads via Tor. If you're going trough that bottleneck, this offers no advantages over a a standard file-sharing service hosted at a .onion node.
ricardobeat 14y ago
And btw, that's basically what Dropbox (and mostly every other private file sharing service) does: files are encrypted using your password as the key.
- dublinben 14y ago
  Even if that's true, Dropbox is still able to access your files at any time. If you don't control the key yourself, it might as well not be encrypted.