The relevant log snippet when opening the file is here: 15:12:48.014 TRACE o.c.f. - Acquired read path lock for ''ġ5:12:48.014 TRACE o.c.f. - Acquired read path lock for ''ġ5:12:48.014 TRACE o.c.f. - Acquired read data lock for ''ġ5:12:48.015 TRACE o.c. - open /Master Thesis/LaTeX/security_evaluation_of_multi-factor_authentication_in_comparison_with_the_web_authentication_api.tex (0)ġ5:12:48.016 TRACE o.c.cryptofs.fh.FileHeaderHolder - Reading file header from /Users/timbrust/Nextcloud/WINGS/d/E7/CJRHFTM7BR6EZDM2BK2JUILOAZGAVL/TAAHMLEY4KSR3JNVVOVOSAGQYTZUOP7C.lngġ5:12:48.016 TRACE o.c.f. - Released read data lock for ''ġ5:12:48.017 TRACE o.c.f. - Released read path lock for ''ġ5:12:48.017 ERROR o.c. - open failed.
#Cryptomator vault free
When posting logs feel free to redact any paths and remove duplicate messages.
run/user/1000/gvfs/afp-volume:host=synology.local,volume=vault/test/d/UD/7BBNL263L2QDIB4ALWJHUWZKGMHWN7/I436DU33AVENZBKWB4AELRKDV2H4WYTSMZXCESA=: Operation not supportedĪt java.base/.UnixFileSystemProvider.newFileChannel(Unknown Source)Ĭaused by: java.io.IOException: Operation not supportedĪt .rite0(Native Method)Īt .rite(FileDispatcherImpl.java:66)Īt .IOUtil.writeFromNativeBuffer(IOUtil.java:89)Īt .IOUtil.write(IOUtil.java:65)Īt .FileChannelImpl.writeInternal(FileChannelImpl.java:778)Īt issue ( : expected ciphertextSize to be positive, but was -88) was discussed in #673 and has an unrelated root cause that should be fixed by We'd need some logs to classify your "symptoms" and check if it is actually related to the OP's issue. The logs attached by show that the low-level I/O API report problems accessing the mounted drive (seems like a permissions issue, possibly mounted with a different user): : /run/user/1000/gvfs/smb-share:server=synology.local,share=vault/test/masterkey.cryptomator: Invalid argumentĪt java.base/.Uni圎anslateToIOException(Unknown Source)Īt java.base/.Uni圎xception.rethrowAsIOException(Unknown Source)Īt java.base/.UnixFileSystemProvider.newByteChannel(Unknown Source)Īt java.base/.FileSystemProvider.newOutputStream(Unknown Source)Īt java.base/.newOutputStream(Unknown Source)Īt java.base/.write(Unknown Source) hosting service provider gives SSH + rsync access to storage and Cryptomator sounds promising in such situation to encrypt data on that storage. In all cases the ciphertextSize value was -88 in log file. : expected ciphertextSize to be positive, but was -88Īt .Preconditions.checkArgument(Preconditions.java:202)Īt .cleartextSize(Cryptors.java:42)Īt .size(CryptoBasicFileAttributes.java:71)Īt .ReadOnlyAdapter.getattr(ReadOnlyAdapter.java:125)Īt ru.$init$1(AbstractFuseFS.java:96)Īt .NativeClosureProxy$$impl$$0.invoke(Unknown Source) Returning a file size of 0.Ġ4:39:28.217 WARN o.c.c.CryptoBasicFileAttributes - Thrown exception was:
This one was several (probably thousands of) times with different data chunks and I got ~32MiB of log file: WARN o.c.c.CryptoBasicFileAttributes - Wrong cipher text file size of file /home/user/webdisk/Pictures/d/Y3/BSB2TJ3DDM6HHV7SYD25KZ2UWAZE2Y/37WTTSF3ZGN27RHRSNXYE2GWYDA5TVRXUWZIW2FODCDLKOHHNQPZETLCXA=.
Some citations from ~/.Cryptomator/cryptomator0.log
0 kommentar(er)
