Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feture Request: Unencrypted mode #142

Open
Che15ea opened this issue Aug 20, 2022 · 4 comments
Open

Feture Request: Unencrypted mode #142

Che15ea opened this issue Aug 20, 2022 · 4 comments

Comments

@Che15ea
Copy link

Che15ea commented Aug 20, 2022

Hi I am a Tor Browser user and I find it very likely to collapse or fail when encrypting in browser for large files. There is also a size limit that Tor Browser can decrypt(a few hundred MB). I never trust front-end encryption anyway. I always encrypt locally myself. I think it would good to introduce a no-javascript unencrypted mode to serve all user's needs. Thank you!

@timvisee
Copy link
Owner

Send is a primarily a browser based file sharing platform. There's no way to implement an end-to-end encrypted system without served cryptography on the front-end.

ffsend (this repository) does not use any JavaScript at all, though. Cryptography is implemented in the tool itself. All encryption/decryption is done on your machine. If you trust its implementation (see source), there's no reason not-to-trust encryption. A Send server has no control over encryption when using ffsend.

If you somehow don't trust the cryptography, you can always encrypt the file before uploading through Send or sending through ffsend.

I see no reason to implement an unencrypted mode.

@Che15ea
Copy link
Author

Che15ea commented Aug 25, 2022

Thank you for your reply! What if the server operator changes the source code? There is no way to verify about that, not like local client which can be verified with PGP.

@timvisee
Copy link
Owner

Thank you for your reply! What if the server operator changes the source code? There is no way to verify about that, not like local client which can be verified with PGP.

That is true. I've stated this in the bottom of the Security section here: https://github.com/timvisee/ffsend#security

@Che15ea
Copy link
Author

Che15ea commented Sep 27, 2022

Since there are some people who don't trust and really rely on front end encryption and decide to encrypt by themselves. I think it is reasonable to implement a unencrypted mode download/upload resumption in order to share big file. There is no other way to share big file stably for tor users.
BTW, it is possible to implement an option not to zip the files, and put them in one link with one password. We may split a big file into dozens and upload and download one by one. Zipping it just made it meaningless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants