- Welcome to Tao Effect Forums.
Recent posts
#11
Espionage 3 / Re: Immediate Auto Lock on Big...
Last post by zsolt - January 28, 2025, 01:57:16 AMHello Scott, did you try to create a new folder and see if it behaves the same?
Cheers
Zsolt
Cheers
Zsolt
#12
Espionage 3 / Re: Immediate Auto Lock on Big...
Last post by greg - January 27, 2025, 12:26:24 PMIf the problem persists with the old version, I'm not sure what to tell you. It sounds like there could be some other software installed on your system that's interfering with Espionage, unmounting the images that it's mounting.
If you email support@taoeffect.com you can try to schedule a remote session with our tech team to troubleshoot more.
If you email support@taoeffect.com you can try to schedule a remote session with our tech team to troubleshoot more.
#13
Espionage 3 / Re: Immediate Auto Lock on Big...
Last post by theFaf - January 26, 2025, 11:12:49 PMHi Greg,
Thank you for the reply and link to the previous version. I installed it, but the problem persists.
Scott
Thank you for the reply and link to the previous version. I installed it, but the problem persists.
Scott
#14
Espionage 3 / Re: Immediate Auto Lock on Big...
Last post by greg - January 26, 2025, 06:32:25 PMHi Scott,
We did not test on Big Sur, and we also did not modify any code related to this, so it's possible something Apple did broke something.
Please try reverting to an older version (which is essentially the same as 3.7.4):
https://www.espionageapp.com/releases/Espionage3.7.3.dmg
We did not test on Big Sur, and we also did not modify any code related to this, so it's possible something Apple did broke something.
Please try reverting to an older version (which is essentially the same as 3.7.4):
https://www.espionageapp.com/releases/Espionage3.7.3.dmg
#15
Espionage 3 / Immediate Auto Lock on Big Sur...
Last post by theFaf - January 26, 2025, 04:21:37 PMI have recently started having a strange issue with Espionage version 3.7.4 on macOS Big Sur (version 11.7.10).
When I unlock a disk image, it unlocks but then immediately locks/unmounts the image. As far as I know, I have done nothing that would have caused the default behavior to change, but Big Sur has been a less-than-great upgrade, so who knows.
I can manually mount the image, but using the Espionage 3 interface it will not stay mounted.
Any ideas?
Thanks!
Scott
When I unlock a disk image, it unlocks but then immediately locks/unmounts the image. As far as I know, I have done nothing that would have caused the default behavior to change, but Big Sur has been a less-than-great upgrade, so who knows.
I can manually mount the image, but using the Espionage 3 interface it will not stay mounted.
Any ideas?
Thanks!
Scott
#16
Espionage 3 / Re: Default disk image locatio...
Last post by carnecro - April 20, 2024, 10:55:13 AMThanks! I just wanted to know where the default image is so I can be sure it is included in my backup.
#17
Espionage 3 / Re: Default disk image locatio...
Last post by greg - April 20, 2024, 10:17:59 AMThe default location is in:
If you want to hide Espionage's existence on your computer, that is not easy to do. Sure, changing the default disk image location can help, but it won't prevent someone from figuring it out. Espionage does not attempt to hide its existence on your computer, and any plausible deniability relies on the fact that some of the disk images are fake.
Code Select
/Users/[username]/Library/Application Support/com.taoeffect.Espionage3/Data
If you want to hide Espionage's existence on your computer, that is not easy to do. Sure, changing the default disk image location can help, but it won't prevent someone from figuring it out. Espionage does not attempt to hide its existence on your computer, and any plausible deniability relies on the fact that some of the disk images are fake.
#18
Espionage 3 / Default disk image location
Last post by carnecro - April 20, 2024, 05:42:22 AMAfter a fresh installation, the default disk image location is 'Data'; unfortunately, the path to the Data folder is not clear. Can anybody tell me the default location, including the path? Is it good practice to change the (probably well-known) location?
Thank you
Robert
Thank you
Robert
#19
Espionage 3 / Re: Can't delete files
Last post by zsolt - February 09, 2024, 12:06:36 AMHello Stevens, dragging a file from the protected folder creates a copy, because MacOS always does a copy when you drag a file from one volume to another (for example if you drag a file from your internal disk to a usb stick or external hard drive). The unlocked folder is in fact a mounted disk image volume which is shown "through" the unlocked folder, but nevertheless, it is another volume.
To change the default behaviour you do exactly what you did.
But the reason I asked is different. If you can "save" your files from the protected folder by copying them into a regular folder, then the simplest way to fix your problem is to copy all the data out of the protected folder, delete the folder from espionage and simply add it anew.
It is a bit of a quick and dirty solution, but it should work. I assume you will not have the same problem with the newly added folder, because it will create the disk image new, reset the permissions and that should make it work.
On the other hand, if you want me to troubleshoot the problem in detail, then we would need a zoom session and I can then take a look into it and try to figure out what went wrong.
If you are fine with the quick fix, then:
- create a new emtpy folder on your internal disk
- unlock the folder in espionage
- drag all the files into the new folder
- ctrl click onto folder in espionage folder list, and select force remove from database
- this will dump the disk image containing the data onto your desktop together with the password file for the disk image
- now drag the new folder to espionage and let it encrypt
- once done, check if all works fine
- if yes, you can trash the disk image and the password file
let me know how it went
Cheers
Zsolt
To change the default behaviour you do exactly what you did.
But the reason I asked is different. If you can "save" your files from the protected folder by copying them into a regular folder, then the simplest way to fix your problem is to copy all the data out of the protected folder, delete the folder from espionage and simply add it anew.
It is a bit of a quick and dirty solution, but it should work. I assume you will not have the same problem with the newly added folder, because it will create the disk image new, reset the permissions and that should make it work.
On the other hand, if you want me to troubleshoot the problem in detail, then we would need a zoom session and I can then take a look into it and try to figure out what went wrong.
If you are fine with the quick fix, then:
- create a new emtpy folder on your internal disk
- unlock the folder in espionage
- drag all the files into the new folder
- ctrl click onto folder in espionage folder list, and select force remove from database
- this will dump the disk image containing the data onto your desktop together with the password file for the disk image
- now drag the new folder to espionage and let it encrypt
- once done, check if all works fine
- if yes, you can trash the disk image and the password file
let me know how it went
Cheers
Zsolt
#20
Espionage 3 / Re: Can't delete files
Last post by stevens - February 08, 2024, 12:30:19 PMI can drag a file from a protected folder into a regular folder. But it leaves a copy behind, which still cannot be moved to the trash.
However I did discover a workaround: if I command-drag the file into a regular folder it moves it without leaving a copy behind. Then I can move the file from the regular folder to the trash.
I can use this workaround but would of course prefer to have things work "properly." So if there is a simple way to adjust something that would let me move a file from a protected (but unlocked) folder directly into the trash, that would be great. Otherwise I can live with what I've got now.
Thanks very much for your quick response to my original post!
However I did discover a workaround: if I command-drag the file into a regular folder it moves it without leaving a copy behind. Then I can move the file from the regular folder to the trash.
I can use this workaround but would of course prefer to have things work "properly." So if there is a simple way to adjust something that would let me move a file from a protected (but unlocked) folder directly into the trash, that would be great. Otherwise I can live with what I've got now.
Thanks very much for your quick response to my original post!