search

bepasty / bepasty-server

universal pastebin server
https://bepasty-server.readthedocs.org/
BSD 2-Clause "Simplified" License
193 stars 46 forks source link

Individually password protect items #81

Open NotANormalNerd opened 10 years ago

NotANormalNerd commented 10 years ago

let the user protect their upload with a password. That could then be given to the downloaders.

ThomasWaldmann commented 10 years ago

yeah, good idea. somehow related to storing encrypted content (if we have such a password, we can encrypt the content). see also #19 but maybe just do it server side (trust in the server required then, so maybe not for everything / everybody). but how do you give the url and the password to the recipient?

NotANormalNerd commented 10 years ago

How do we ensure encryption? It probably would be better if user encrypt content by themselves and send the key or password by mail or something else. Encryption by US would only be a nice Gimmick.

ThomasWaldmann commented 10 years ago

Sure, for server-side encryption (and also for server-side password protection), you need to trust the server.

Depending on who owns / administrates the server, that might be an option or not.

Marwe commented 7 years ago

I like the approach of zerobin, with client side encryption and the key in the URL anchor, so it is never sent to the server. An active fork is Privatebin. Maybe this can be integrated or bepasty be a backend for binary files, which are not supported there.

ThomasWaldmann commented 7 years ago

A binary pastebin must scale to big files, not sure if the zerobin/privatebin code scales to potentially many hundred MB or even GBs.