search

goh-chunlin / onesync

Automatically exported from code.google.com/p/onesync
1 stars 0 forks source link

Syncing fails when processing encrypted files #152

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a Sync job where the source folder is on an NTFS partition, and 
contains at least one file with the "Encrypt contents" flag enabled.
2. The intermediate storage location should be one that does NOT support NTFS 
encryption, such as FAT32 or some other FS type.
3. Start the sync process for this job

What is the expected output? What do you see instead?
OneSync should synchronize the files between the source folder and the 
intermidiate storage location.  Instead, it syncs unencrypted files 
successfully until an encrypted file is encountered, at which point it fails.  

What version of the product are you using? On what operating system?
OneSync 3, running on Windows Vista SP2 and an NTFS-partitioned hard drive.

Please provide any additional information below.
The encrypted files that I am attempting to sync are files that I can decrypt 
successfully.  They are decrypted automatically while logged in (and the 
appropriate certificate is available), and can [normally] be accessed 
transparently by any process that accesses the file on disk.

I will make an attempt to sync encrypted files where the intermediate storage 
location is ALSO on an NTFS partition, and see if that changes the outcome.

Original issue reported on code.google.com by daniel.h...@gmail.com on 9 Dec 2010 at 8:52

GoogleCodeExporter commented 8 years ago 
UPDATE
I attempted to recreate the issue in a controlled manner.  To do so, I created 
three sync source directories.  One that was completely unencrypted, one that 
was completely encrypted, and one that had a mix of encrypted and non-encrypted 
files.

All three sources successfully synced with intermediate storage directories on 
the same NTFS drive, with the encryption flag set properly on the data files.  
When syncing to a location that did not allow for encryption, the two sources 
with encrypted files reported failure during sync.  Logs are attached.  In the 
targets for the two failed sync jobs, there are NO files under the "files" 
directory.

Original comment by daniel.h...@gmail.com on 10 Dec 2010 at 4:15

Attachments:

GoogleCodeExporter commented 8 years ago 
So, it is caused by the locations which do not support NTFS encryption. Thanks 
for informing this problem that we did not discover. We will look into this 
problem and update you with our findings.

Original comment by gclin...@gmail.com on 2 Feb 2011 at 5:17