Win 10 Pro 2004 (build 19041.630). Latest version of Cryptomator mounted via Dokany. Vault is located in Google Drive and synced via Google’s Sync & Backup application.
I like backup the contents of my unencrypted vault on a regular basis. My process is to use 7zip to archive the contents of the vault into a .ZIP file on my C:\ drive before copying it to a USB HDD. I ran into a file access failure with a specific file in my vault. The interesting thing is that I have this access failure if I try to copy this unencrypted file to my C: drive as well.
Log contents:
17:28:29.095 [main] INFO org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Windows 10 10.0 (amd64)
17:28:29.945 [JavaFX Application Thread] INFO o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
17:28:29.975 [JavaFX Application Thread] INFO org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
17:28:34.963 [JavaFX Application Thread] WARN o.c.keychain.KeychainManager - LOAD
17:28:36.969 [JavaFX Application Thread] INFO o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.5.8, lastest version: 1.5.8
17:28:41.639 [App Background Thread 004] INFO com.dokany.java.DokanyDriver - Dokany version: 140
17:28:41.640 [App Background Thread 004] INFO com.dokany.java.DokanyDriver - Dokany driver version: 400
17:28:44.643 [App Background Thread 004] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of 'MyVault' succeeded.
17:29:12.165 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Revealed MyVault
17:31:30.320 [Thread-113943] WARN o.c.frontend.dokany.ReadWriteAdapter - (7673) readFile(): IO error while reading file /Telegram/tdata/user_data/cache/0/binlog.
{}
java.io.IOException: org.cryptomator.cryptolib.api.AuthenticationFailedException: Authentication of chunk 8 failed.
at org.cryptomator.cryptofs.fh.ChunkCache.get(ChunkCache.java:67)
at org.cryptomator.cryptofs.ch.CleartextFileChannel.readLocked(CleartextFileChannel.java:109)
at org.cryptomator.cryptofs.ch.AbstractFileChannel.read(AbstractFileChannel.java:155)
at org.cryptomator.cryptofs.ch.AbstractFileChannel.read(AbstractFileChannel.java:139)
at org.cryptomator.frontend.dokany.OpenFile.readNext(OpenFile.java:95)
at org.cryptomator.frontend.dokany.OpenFile.read(OpenFile.java:49)
at org.cryptomator.frontend.dokany.ReadWriteAdapter.readFile(ReadWriteAdapter.java:335)
at com.dokany.java.DokanyOperationsProxy$ReadFileProxy.callback(DokanyOperationsProxy.java:86)
at jdk.internal.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.jna.CallbackReference$DefaultCallbackProxy.invokeCallback(CallbackReference.java:520)
at com.sun.jna.CallbackReference$DefaultCallbackProxy.callback(CallbackReference.java:551)
Caused by: org.cryptomator.cryptolib.api.AuthenticationFailedException: Authentication of chunk 8 failed.
at org.cryptomator.cryptolib.v1.FileContentCryptorImpl.decryptChunk(FileContentCryptorImpl.java:71)
at org.cryptomator.cryptofs.fh.ChunkLoader.load(ChunkLoader.java:38)
at org.cryptomator.cryptofs.fh.ChunkCache.loadChunk(ChunkCache.java:40)
at com.google.common.cache.CacheLoader$FunctionToCacheLoader.load(CacheLoader.java:165)
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3529)
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2278)
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2155)
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2045)
at com.google.common.cache.LocalCache.get(LocalCache.java:3951)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974)
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4958)
at org.cryptomator.cryptofs.fh.ChunkCache.get(ChunkCache.java:57)
Any ideas on what’s causing this access failure? For what it’s worth, Telegram runs just fine out of my vault. I’ve never encountered this problem when attempting to run Telegram.
I said that I don’t have an issue with running Telegram out of my vault. That is correct. However, in looking at today’s log file, it looks like a similar error does appear when attempting to run Telegram:
09:14:54.491 [main] INFO org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Windows 10 10.0 (amd64)
09:14:55.757 [JavaFX Application Thread] INFO o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
09:14:55.797 [JavaFX Application Thread] INFO org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
09:15:03.382 [JavaFX Application Thread] INFO o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.5.8, lastest version: 1.5.8
09:15:14.280 [JavaFX Application Thread] WARN o.c.keychain.KeychainManager - LOAD
09:15:21.944 [App Background Thread 004] INFO com.dokany.java.DokanyDriver - Dokany version: 140
09:15:21.944 [App Background Thread 004] INFO com.dokany.java.DokanyDriver - Dokany driver version: 400
09:15:24.949 [App Background Thread 004] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of 'MyVault' succeeded.
09:32:52.004 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Revealed MyVault
09:33:16.470 [Thread-7960] WARN o.c.frontend.dokany.ReadWriteAdapter - (1615) readFile(): IO error while reading file /Telegram/tdata/user_data/cache/0/binlog.
{}
java.io.IOException: org.cryptomator.cryptolib.api.AuthenticationFailedException: Authentication of chunk 8 failed.
at org.cryptomator.cryptofs.fh.ChunkCache.get(ChunkCache.java:67)
at org.cryptomator.cryptofs.ch.CleartextFileChannel.readLocked(CleartextFileChannel.java:109)
at org.cryptomator.cryptofs.ch.AbstractFileChannel.read(AbstractFileChannel.java:155)
at org.cryptomator.cryptofs.ch.AbstractFileChannel.read(AbstractFileChannel.java:139)
at org.cryptomator.frontend.dokany.OpenFile.readNext(OpenFile.java:95)
at org.cryptomator.frontend.dokany.OpenFile.read(OpenFile.java:49)
at org.cryptomator.frontend.dokany.ReadWriteAdapter.readFile(ReadWriteAdapter.java:335)
at com.dokany.java.DokanyOperationsProxy$ReadFileProxy.callback(DokanyOperationsProxy.java:86)
at jdk.internal.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.jna.CallbackReference$DefaultCallbackProxy.invokeCallback(CallbackReference.java:520)
at com.sun.jna.CallbackReference$DefaultCallbackProxy.callback(CallbackReference.java:551)
Caused by: org.cryptomator.cryptolib.api.AuthenticationFailedException: Authentication of chunk 8 failed.
at org.cryptomator.cryptolib.v1.FileContentCryptorImpl.decryptChunk(FileContentCryptorImpl.java:71)
at org.cryptomator.cryptofs.fh.ChunkLoader.load(ChunkLoader.java:38)
at org.cryptomator.cryptofs.fh.ChunkCache.loadChunk(ChunkCache.java:40)
at com.google.common.cache.CacheLoader$FunctionToCacheLoader.load(CacheLoader.java:165)
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3529)
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2278)
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2155)
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2045)
at com.google.common.cache.LocalCache.get(LocalCache.java:3951)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974)
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4958)
at org.cryptomator.cryptofs.fh.ChunkCache.get(ChunkCache.java:57)
... 12 common frames omitted
09:33:16.482 [Thread-8000] WARN o.c.frontend.dokany.ReadWriteAdapter - (1615) readFile(): IO error while reading file /Telegram/tdata/user_data/cache/0/binlog.
{}
java.io.IOException: org.cryptomator.cryptolib.api.AuthenticationFailedException: Authentication of chunk 8 failed.
at org.cryptomator.cryptofs.fh.ChunkCache.get(ChunkCache.java:67)
at org.cryptomator.cryptofs.ch.CleartextFileChannel.readLocked(CleartextFileChannel.java:109)
at org.cryptomator.cryptofs.ch.AbstractFileChannel.read(AbstractFileChannel.java:155)
at org.cryptomator.cryptofs.ch.AbstractFileChannel.read(AbstractFileChannel.java:139)
at org.cryptomator.frontend.dokany.OpenFile.readNext(OpenFile.java:95)
at org.cryptomator.frontend.dokany.OpenFile.read(OpenFile.java:49)
at org.cryptomator.frontend.dokany.ReadWriteAdapter.readFile(ReadWriteAdapter.java:335)
at com.dokany.java.DokanyOperationsProxy$ReadFileProxy.callback(DokanyOperationsProxy.java:86)
at jdk.internal.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.jna.CallbackReference$DefaultCallbackProxy.invokeCallback(CallbackReference.java:520)
at com.sun.jna.CallbackReference$DefaultCallbackProxy.callback(CallbackReference.java:551)
Caused by: org.cryptomator.cryptolib.api.AuthenticationFailedException: Authentication of chunk 8 failed.
at org.cryptomator.cryptolib.v1.FileContentCryptorImpl.decryptChunk(FileContentCryptorImpl.java:71)
at org.cryptomator.cryptofs.fh.ChunkLoader.load(ChunkLoader.java:38)
at org.cryptomator.cryptofs.fh.ChunkCache.loadChunk(ChunkCache.java:40)
at com.google.common.cache.CacheLoader$FunctionToCacheLoader.load(CacheLoader.java:165)
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3529)
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2278)
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2155)
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2045)
at com.google.common.cache.LocalCache.get(LocalCache.java:3951)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974)
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4958)
at org.cryptomator.cryptofs.fh.ChunkCache.get(ChunkCache.java:57)
... 12 common frames omitted
I realize time has passed, but since your post got no replies when originally posted, why not?
64-bit Windows 10 machine
Today is the 2nd time I have had issues with file access on Cryptomator. Today, I used Google Photos to export 6 photos to a Cryptomator vault folder. When I touched the file to unzip it, I got the blue timer circle. After several minutes, I knew I had a problem, as nothing was happening.
I quit Cryptomator and went back in. Same thing, opening that folder now gives me the blue circle. I rebooted the PC. Same thing, it’s locked up.
So I used a command prompt, navigated there, and was able to delete the file that way.
This is the 2nd time this has happened with zip files. It’s as if I can’t do zip work on a Cryptomator drive. That makes this tool useless to me.
I’m now searching for some other practice that doesn’t involve encrypted drives but still keeps my data protected. Walking away from Cryptomator, I can’t deal with these issues and no one paying attention.