News for hackers. Stuff that matters.
Re:Pwncloud – Bad crypto in the Owncloud encryption module by schlowmo on Sunday April 10, 2016 @04:43PM (#11468081)
> "First it is important to understand what this encryption module is actually supposed to do and understand the threat scenario. The encryption provides no security against a malicious server operator, because the encryption happens on the server. The only scenario where this encryption helps is if one has a trusted server that is using an untrusted storage space."

While it's a good finding that even in this specific scenario the crypto-module is screwed up, I think an even bigger problem is that most people hosting owncloud either don't know or care about all threats not covered by this scenario.

I heard stuff like "Owncloud has crypto, so it must be secure." from people hosting owncloud on server they didn't have much control (especially physically) about. It's not only the "malicious server operator" but everyone with administrative access (legitimate or not) to this server.

But unfortunately I don't know a selfhosted easy-to-install-and-use alternative with strong client-side encryption, which boils down to: Dropbox (or any other cloud storage provider) with client-side encryption of your own choice is more secure than owncloud with only the crypto-module.

Re:Pwncloud – Bad crypto in the Owncloud encryption module by drdaeman on Sunday April 10, 2016 @06:48PM (#11468561)
For those who aren't afraid of manual control (which can be a pro or con) and a bit cryptic CLI invocations, I'd say - give git-annex a try.

It works with multiple remotes (hubiC, OneDrive and SFTP) flawlessly for me.

A basic file management is well automated by git-annex-assistant (e.g. just moving a file to "archive" directory makes sure necessary number of remotes have a copy and a local one is then removed, etc etc.), but the initial setup has to be done by a tech-savvy person who had spent some time reading the docs.

Re:Pwncloud – Bad crypto in the Owncloud encryption module by fapjacks on Sunday April 10, 2016 @05:44PM (#11468321)
I just want to add a big emphasis to "YOUR OWN CRYPTO" with Dropbox. Stuffing data into Dropbox without encrypting it first for example with VeraCrypt is a bad choice. Even Dropbox says their own employees "need" access to your data "occasionally". (Also, I meant to upvote you but I fat-fingered it on my phone, sorry!)
Re:Pwncloud – Bad crypto in the Owncloud encryption module by drdaeman on Sunday April 10, 2016 @06:52PM (#11468579)
VeraCrypt or other FDE-like tools (that are meant to be used on actual drives or their imitations using a file-backed device) are not so great idea for use with Dropbox or alike file/object storages. Here's why: http://sockpuppet.org/blog/2014/04/30/you-dont-want-xts/
Re:Pwncloud – Bad crypto in the Owncloud encryption module by netheril96 on Sunday April 10, 2016 @11:51PM (#11469514)
Time to promote my project `securefs` again (https://github.com/netheril96/securefs). Written specifically to address that XTS issue.
Re:Pwncloud – Bad crypto in the Owncloud encryption module by giovannibajo1 on Sunday April 10, 2016 @10:17PM (#11469242)
Is there a client side encryption tool that works with Dropbox and is usable by non technical people (plus for being available on both Windows and Mac)?

I personally use encfs to create a partition within Dropbox, but I don't see that being easy to setup and manage...

Re:Pwncloud – Bad crypto in the Owncloud encryption module by dublinben on Sunday April 10, 2016 @10:31PM (#11469294)
EncFS is specifically not safe to use in situations where an attacker has multiple versions of your data.
Re:Pwncloud – Bad crypto in the Owncloud encryption module by g_p on Monday April 11, 2016 @02:22AM (#11469943)
Cryptomator [1] looks like it fits the bill for what you described. Seems to use a transparent mapped virtual WebDAV drive to make it usable. From my experiments at least, it seems it should be usable by non-technical people without significant demonstration or training.

[1] https://github.com/cryptomator/cryptomator

Re:Pwncloud – Bad crypto in the Owncloud encryption module by schlowmo on Sunday April 10, 2016 @06:53PM (#11468581)
Yes, maybe I should've made this emphasis stronger in my comment. Also I didn't meant to say that using owncloud is worse than using dropbox in security terms - but you should use your own (client-side) crypto either way if you care about data security.

For myself I use my selfhosted owncloud (running on a cheap VPS) with EncFS, encourage other users on that server to use client-side encryption as well and never lied about how secure their data is when they decide not to. But this isn't so easy as it should be.

Re:Pwncloud – Bad crypto in the Owncloud encryption module by bigiain on Sunday April 10, 2016 @10:34PM (#11469302)
I also use EncFS - on Dropbox/GoogleDrive/JottaCloud - but be aware it's got known flaws, don't rely on it if your data might be of interest to a nation state or high level law enforcement: https://defuse.ca/audits/encfs.htm
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
Re:Pwncloud – Bad crypto in the Owncloud encryption module by danieldk on Monday April 11, 2016 @02:14AM (#11469925)
Bittorrent Sync does end to end encryption, and you can set up an encrypted read-only peer that never sees any plain text. The encrypted peer does contribute to the swarm.
Re:Pwncloud – Bad crypto in the Owncloud encryption module by Tepix on Monday April 11, 2016 @08:00AM (#11470929)
It's closed source.
Re:Pwncloud – Bad crypto in the Owncloud encryption module by danieldk on Monday April 11, 2016 @08:08AM (#11470960)
Sadly, yes. So if anyone is looking for a nice disruptive open source project ;).

(No, SyncThing, despite its greatness is not it. The sharing model is too complex for the average user.)

Re:Pwncloud – Bad crypto in the Owncloud encryption module by educar on Sunday April 10, 2016 @07:49PM (#11468774)
Well, you can use client side encryption with Owncloud as well. What makes dropbox special?
Re:Pwncloud – Bad crypto in the Owncloud encryption module by schlowmo on Monday April 11, 2016 @07:01AM (#11470708)
> "or any other cloud storage provider"

I just wanted to point out that as long as you're not in full control of the server hosting Owncloud (and not connect your Owncloud to third party cloud spaces) you've to care about your own client-side crypto like on any other cloud provider (self hosted or not). So there's nothing special about Dropbox - but also not so much special in security terms about Owncloud.

Anyway I would still recommend using Owncloud over any other cloud storage provider if you're able to host it or know someone hosting it. But you should consider the security implications if you care.