#127 Copies of Encrypted Files appear in Recycle Bin

[Anonymous]

Originally created by: mi...@morphodesigns.com

What steps will reproduce the problem?
1. I have no idea why this happens, these are files that haven't been accessed in two years. (They were synced more recently, of course, but the point is, they are inactive files.)
2. ACTUALLY... after putting this together, I realized that the only thing all 7 files have in common, regardless of whether they are in source, destination or recycle bin: a LEADING SPACE. So, maybe try syncing files with leading spaces to reproduce...
3.

What is the expected output? What do you see instead?
I certainly don't expect to see Encrypted synced files in Recycle Bin unless I delete them from the source (unencrypted) folders.

What version of the product are you using? On what operating system?
CryptSync 1.2.0.264 on Windows 7 (32-bit)

Please provide any additional information below.
I always assumed the recycle bin was being filled as I deleted or moved files out of the source folders. But I happened to check some file names and couldn't figure out why they had been sent to the Recycle Bin.

Especially puzzling is the fact that the original pairs are still in their respective Unencrypted and Encrypted folders. (I assume that they are originals, since the dates haven't changed.)

[Anonymous]

Originally posted by: mi...@morphodesigns.com

I looked in the log and found these two lines - for the chess game file:

07/18/14 04:57:18 : encrypt file C:\Users\MA\Documents\AA Cloud\zzzArchive\Chess\ g1105161742 rhometal-anklebuster 0-1.pgn to C:\Users\MA\Google Drive\!Vault\zzzArchive\Chess\ g1105161742 rhometal-anklebuster 0-1.pgn.7z

07/18/14 04:57:22 : counterpart of file zzzArchive\Chess\g1105161742 rhometal-anklebuster 0-1.pgn does not exist in src folder, delete file

You can see that the space is the issue differentiating these. So, should we avoid file names with leading spaces?

[Anonymous]

Originally posted by: tortoisesvn

Yes, the problem is with the leading space in the filename.
Unfortunately, 7zip does not allow filenames be created with those, it automatically strips leading and trailing spaces when it creates the *.7z file.

Also, such filenames are not handled by the windows explorer properly either, so you really shouldn't use such filenames.

[Anonymous]

Originally posted by: mi...@morphodesigns.com

Thanks for letting me know the sources of the problem. I do a lot of copy/paste and I suppose I get the errant space now and then. However, until I tested renaming, I never realized that Windows Explorer couldn't handle the spaces! Sheesh, right?

Cheers,

Mitch