End-to-end encrypted file sharing
Web client
•
Server
•
Submit an Issue
blindsend is an open source tool for private, end-to-end encrypted file exchange.
It supports two use cases - sharing files and requesting files.
You can find the protocol description in the protocol.pdf file.
A demo can be found on https://blindsend.io.
You will start by uploading files and obtaining a link to download. You can then share the link with anyone and they will be able to download the files.
We call this the Share file use case.
If you are sharing the link via an unsecure channel like facebook messenger, a password can be set to additionally improve the security. You should share the password using a different secure channel, for example, in person.
If you need someone to send you a file, you will generate a request link and send it to that person. They will open the link and upload the requested files, after which you can access the same link to download the files.
We call this the Request file use case.
Similar to the sharing files use-case, you can set a password which needs to be input again when downloading files.
This use-case is suitable for various professional services, such as doctors asking for blood results or a lawyer asking for a subpoena.
Traditionally, those documents were shared using an insecure channel such as email.
Blindsend consists of four parts:
- Server, which provides the REST API for managing file exchange workflows.
- Web UI, which handles encryption and decryption of files on agents' local machines, and provides a web client.
- Cloud Storage on the Google Cloud platform where the encrypted files are stored.
- PostgreSQL where link data is stored.
Files uploaded to blindsend are encrypted using an end-to-end encrypted protocol, meaning neither blindsend nor any third party can decrypt them.
Only the persons possessing the link (and an optional password) can decrypt the files.
It is important to share the link using an authenticated channel, meaning the link wasn’t changed during the transfer and the other party receives the same link you sent them.
If the channel is not secure, a password can be set to prevent the third party from decrypting the files.
To keep sensitive information away from the blindsend servers, links use the URL fragments. They are the parts of the URL after the # symbol which are not sent to the server when the URL is opened in the browser.
Protocol diagrams are coming soon!
- Currently, the files are deleted after 7 days.
- Add the option to set custom file expiration date.
- File deletion policy can be based on the number of times the file was opened.
- Specify your email address to receive the access logs.
- Specify another user’s email address who will receive a link.
blindsend is under development by a team of software engineers at blindnet.io and several independent cryptography experts.
All community participation is subject to blindnet’s Code of Conduct.
Stay up to date with new releases and projects, learn more about how to protect your privacy and that of our users, and share projects and feedback with our team.
- Join our Slack Workspace to chat with the blindnet community and team
- Follow us on Twitter to stay up to date with the latest news
- Check out our Openness Framework and Product Management on Github to see how we operate and give us feedback.
The blindsend-server is available under MIT (and here is why). You are free to deploy your own instances. Contact us if you need any help at blindsend@blindnet.io