https://github.com/haiwen/ccnet/issues/35
/* truly random sequece read from /dev/urandom. */
static unsigned char salt[8] = { 0xdb, 0x91, 0x45, 0xc3, 0x06, 0xc7, 0xcc, 0x26 };
https://github.com/haiwen/seafile/issues/587Enough to understand if people writing this software know how to apply cryptography. This was 2 years ago, so I hope they improved.
Seafile stores a lot of metadata in clear text (including filenames): https://github.com/haiwen/seafile/issues/350
The developers know about it, the issue is 3 years old, this huge limitation is still not reflected on their documentation.
An attacker who obtains a copy of the encrypted library without the key can:
- read the complete list of directory and file names.
- know the size of every file
- know which files share some of the same information
- see the history of who changed each file, when, and what byte ranges were altered> We don't roll our own crypto.
> There are two parts of the code base in which "we roll our own crypto": the transfer protocl and encrypted library.
That's just ridiculous.
About metadata : https://seacloud.cc/group/3/wiki/seafile-roadmap.md there is one line saying "Ability to encrypt all data by server key. Key has to be generated by administrator" but it's not on the changelog page ( https://seacloud.cc/group/3/wiki/Server%20ChangeLog.md )
Incredible that people will actually do this in production code. I don't understand a lot about cryptography, and even I know this not a good idea.
Easy to install and to upgrade (except a small glitch in the last upgrade).
For the community version, the source code is here : https://github.com/haiwen/seafile (see others haiwen projects).
The Android client could be improved, but it does the job.