by zsolt » Mon Apr 16, 2012 7:30 pm
So for those interested, before coming to the problem itself, I have to briefly explain how Espionage works.
Say you have a folder named myfolder, and insider myfolder there are myfile1 and myfile2.
Once you add myfolder to Espionage, it will create an encrypted and hidden disk image, name it myfolder, copy the myfile1 and myfile2 into it, and move the original files to the trash.
So when myfolder is locked, it will be a regular folder, but will contain a hidden disk image. Espionage is monitoring click requests to this folder.
Once you click on it, or an application tries to access the content, Espionage will detect this and prompt for pass.
Once the pass is entered it will unlock the folder. But what will in fact happen is this:
- it will move the disk image into the parent folder of myfolder, open the disk image and mount it, and create a symlink named myfolder, pointing to the mounted disk image.
-----------------------------------
now to the problem:
- if you understand what I wrote above, then you realize that the disk image is either in the myfolder, when the myfolder is locked, or it is in the parent folder of myfolder, when the folder is unlocked.
Well, in this case, it was BOTH inside myfolder and parent folder. So on lock request, Espionage should have move the disk image from parent folder into the myfolder, but detected that inside myfolder there is already a disk image with the same name, and to avoid data loss by deleting the disk image, it stop and issued the warning.
Customer disabled the folder in espionage, mounted each disk image, figured out which one is right, deleted the other one and enabled the folder again in Espionage. But if this happens to you, I suggest you open a support ticket so that we verify the things before you proceed deleting things.
Cheers,
Zsolt
Follow for news! | For general Mac support, please visit