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

[SECURITY] Client-Side encryption not working #824

Closed
jonaysanz opened this issue Aug 29, 2014 · 8 comments
Closed

[SECURITY] Client-Side encryption not working #824

jonaysanz opened this issue Aug 29, 2014 · 8 comments

Comments

@jonaysanz
Copy link

Client-Side encryption is not working. My files are been uploaded in a plain way.

Steps to reproduce it:
1- Install and deploy seafile on your computer
2- Do not use HTTPS. Only plain HTTP
3- Write a TXT file with any content
4- Open WireShark to capture network requests
5- Upload file

On WireShark you can see in a request your TXT file

@freeplant
Copy link
Member

Use encrypted library.

@jonaysanz
Copy link
Author

how? I cannot find how to do it

@freeplant
Copy link
Member

When you create a library, choose the option of encryption

@jonaysanz jonaysanz changed the title Client-Side encryption not working [SECURITY] Client-Side encryption not working Aug 30, 2014
@jonaysanz
Copy link
Author

There's a Securrity Issue on client-side encryption.
It does not encrypt anything, even the library is encrypted.

I uploaded a video with my test. If isn't like this, explain me. I used encrypted library.

http://youtu.be/whean7YFwko

@freeplant
Copy link
Member

I get what you are talking about now. Client side encryption only work when you sync files via the desktop client. We have removed the support of client side encryption via web browser. It is hard to maintain.

@delin
Copy link

delin commented Jan 20, 2015

When uploading files via the browser(with and without ssl) in an encrypted library, it will be stored encrypted on the server?

@shoeper
Copy link
Collaborator

shoeper commented Jan 20, 2015

afaik your key will be cached on the server for one hour in this case and the servery encrypts your data. So you should use ssl for that. And you should trust the server running seafile otherwise it would be better not to type in your enrypted library password in the browser (which sends it to the server to encrypt your files there).

@delin
Copy link

delin commented Jan 21, 2015

@shoeper thx!

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

4 participants