Introduction
Managing files and folders
- Managing files with libraries
- Restoring deleted files
- Finding old file versions
- Library history and snapshots
- Setting history retention period
- Deleting a library
- Viewing files within Web App
- Full text file search
Sharing and collaboration
Wiki and knowledge management
Desktop client and syncing
- Install and sync files
- Syncing existing folders
- Selectively sync sub-folders
- Read-only syncing
- Unsync and resync libraries
- Setting sync interval
- Proxy settings
- File conflicts
- Excluding files
Drive client
Security and encryption
How to Use Encrypted Libraries
Seafile provides client-side end-to-end data encryption. You can create encrypted libraries to use this feature. File contents in encrypted libraries are encrypted on client side. The encryption password is not stored on the server. So even the server administrator can't access your file contents.
When creating an encrypted library:
- If you create an encrypted library in the web app, the password is sent to the server. The server uses this password to create the library. But it doesn't store the plain text password.
- If you create an encrypted library from a local folder with the desktop client (see file syncing), the password is not sent to the server.
When you access the encrypted library:
- If you use web app, you have to input the password to the server. The server will cache the password in encrypted format for 1 hour. It won't store the password on disk.
- If you use desktop client to sync the library, the password is not sent to the server. The client decrypts and encrypts file contents locally. The plain text password is not stored on the client disk either.
- iOS client supports client side encryption since version 2.1.6. Android client supports it since version 2.1.0.
Note that encrypted library only encrypts the contents of the files, but not the folder and file names.