Ownclound Client and local encryption

ymolinet · December 21, 2016, 8:01am

Hi all,

I’m use a encryption software to protect my data on my laptop (only folders, not the full disk) and I want to use OC Windows Client to sync some of this data in their uncrypted state. How can I be sure that the owncloud windows client wait for the local folder is open (by the encryption software) before start to sync ?

Thanks,
Yannick

alfageme · December 21, 2016, 9:35am

Hi @ymolinet!

I’ve already seen many people reporting to be using local encryption, it’s definitely a hot topic for people interested in data safety. Just out of curiosity, which encryption software are you using?

The desktop client team is working right now in a fix that might help you if you use a system based on unencrypted mounting points (e.g. VeraCrypt):

github.com/owncloud/client

[Windows] [2.2.4 build 6408] does not re-include unavailable local sync folders when they are available again.

opened 09:11AM - 16 Nov 16 UTC

closed 11:44AM - 09 Jan 17 UTC

TDannhauer

type:bug ReadyToTest

### Expected behaviour After adding a folder sync to a removable drive (e.g. st…ick or Veracrypt container), the client complains after system boot: It marks the unaccessible folder with a read cross and says "Unable to find local sync folder." After making the missing folder accessible, ( e.g. mounting the encrypted device), the missing folder should be re-evaluated (time or event based) by the OC client and included into sync activities as soon as it is available again. This would make it convenient to setup local sync folders on encrypted devices. ### Actual behaviour However, after making the missing folder accessible, ( e.g. mounting the encrypted device) does not re-enable syncronisation for that folder. Only manually pausing and resuming sync triggers the OC client to re-evaluate the folder, to find it and to re-enable its synchronisation. ### Steps to reproduce 1. Setup a folder syncronisation on a accessible removable drive (like a Truecrypt/veracrypt container) 2. Make drive unaccessible at bootup. 3. Setup Owncloud Client to auto start at user login 4. Reboot system 5. Look at Owncloud client: It marks the unaccessible folder with a read cross and says "Unable to find local sync folder." 6. Make folder accessible again, e.g. by mounting it in Veracrypt 7. Look at Owncloud client: It still marks the unaccessible folder with a read cross and says "Unable to find local sync folder.". 8. Pause sync for that folder manually. 9. Resume sync for that folder manually. 10. Look at Owncloud client: It now finds the accessible folder and re-enables sync for that folder. ### Server configuration Operating system: Debian Jessie Web server: Apache 2.4.10 Database: Postgres 9.3 PHP version: PHP-FPM 5.6.27 ownCloud version: 9.1.2 Storage backend (external storage): none ### Client configuration Client version: 2.2.4 build 6408 Operating system: Win10 64 bit OS language: DE Installation path of client: C:\Program Files (x86)\ownCloud

After this is implemented, once you have your local folder (drive) unlocked by the enc. software, the client will start syncing again. How does that sound?

Best,
Samuel

ymolinet · December 22, 2016, 11:55pm

I’m using ESET DESLOCK+ PRO.
What is the impact if I try to crypt the root folder of the data sync (root folder contains the db files) ? When running, the owncloud client could not open the files (db) because it’s crypted so sync could not start ?

tflidd · December 23, 2016, 8:04am

There is already a pull request linked to this issue. Not sure if it is worth testing it.
@ogoffart

guruz · January 5, 2017, 2:26pm

@ymolinet Do you also want to test the nightly? [Windows] [2.2.4 build 6408] does not re-include unavailable local sync folders when they are available again. · Issue #5317 · owncloud/client · GitHub