Hi,
Though I have locked the cryptomator vault, I am still able to open Excel files via file reference.
I am using a Cryptomator-vault in a VeraCrypt-Container. Even if I
lock the Cryptomator-Vault
unmount the VeraCrypt-Container
Mount it VeraCrypt-Container
I am able to open Excel files via file reference.
what do you expect? you’re using windows 10 lmao. ofc everything is completely unprotected.
as soon as you decrypt/view any files, windows will cache it and whatever. there’s probably some settings to disable the cache but it’s tricky to have any real privacy
Cryptomator is not designed to encrypt your local system. It’s designed for online storages. If you want to have local encryption, then I recommend you veracrypt (as you already use it) and encrypt the complete partitions of your System.
Thank you Michael. I did not know this before.
I want to use a container in a container. Because I have private files to be strongly separated from the other files.
This is why I used Cryptomator-Container in VeraCrypt-Container. What solution would you recommend?
Thank yo OverHeadHunter, I changed the “Laufwerkseinbindung” Method (I assume in english this is drive mounting or drive integration) from Dokany to WebDav and this solved the problem.
With WebDav I can no longer load encrypted files by just using the file reference.
If you want to store these files online I would recommend 2 Cryptomator vaults. If you are operating only local I would rather go with 2 veracrypt container.
I have another question for this case: What is a file reference? Is this a shortcut to a file (windows *.lnk file)? Or something else? Because maybe this error is specific to these “references” and should be further investigated.