News for hackers. Stuff that matters.
Re:Pwncloud – Bad crypto in the Owncloud encryption module by JohnIcare on Monday April 11, 2016 @12:45AM (#11469691)
There is seafile ( https://www.seafile.com/en/home/ ) which provides client side encryption.

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.

Re:Pwncloud – Bad crypto in the Owncloud encryption module by dchest on Monday April 11, 2016 @02:12AM (#11469919)
This issue in Seafile was lovely:

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/587

Enough to understand if people writing this software know how to apply cryptography. This was 2 years ago, so I hope they improved.

Re:Pwncloud – Bad crypto in the Owncloud encryption module by Kunix on Monday April 11, 2016 @06:08AM (#11470553)
I would strongly recommend against using Seafile.

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
Re:Pwncloud – Bad crypto in the Owncloud encryption module by Semaphor on Monday April 11, 2016 @04:33AM (#11470310)
What seems truly scary is how little the developer seemed to care about those security bugs (following related issues, you also find an exploit, SQL injection and so on) and being dismissive of the guy who found them.
Re:Pwncloud – Bad crypto in the Owncloud encryption module by embik on Monday April 11, 2016 @05:45AM (#11470484)
https://github.com/haiwen/seafile/issues/587#issuecomment-40...

> 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.

Re:Pwncloud – Bad crypto in the Owncloud encryption module by JohnIcare on Monday April 11, 2016 @07:30AM (#11470805)
For information : since that github comment, now the protocol relies only on HTTPS.

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 )

Re:Pwncloud – Bad crypto in the Owncloud encryption module by Artemis2 on Monday April 11, 2016 @02:41AM (#11469979)
Re:Pwncloud – Bad crypto in the Owncloud encryption module by krylon on Monday April 11, 2016 @05:05AM (#11470387)
Thanks for saving me from having to look that one up.

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.

Re:Pwncloud – Bad crypto in the Owncloud encryption module by dspillett on Monday April 11, 2016 @06:33AM (#11470610)
Also, though less exactly relevant: http://dilbert.com/strip/2001-10-25
Re:Pwncloud – Bad crypto in the Owncloud encryption module by xjqkilling on Monday April 11, 2016 @10:36PM (#11476834)
This was 2 years ago. The situation is much better now. You can find how Seafile handles user passwords at http://manual.seafile.com/security/security_features.html