![]() ![]() ![]() And "normal" users will neither look at nor open GitHub cp -a ~/Dropbox/DOSBox/C.Win311/WINDOWS/SYSTEM/WING32.DLL diff ~/Dropbox/DOSBox/C.Win311/WINDOWS/SYSTEM/WING32.DLL cp -a. non-terminal) applications, and users might be wondering why their stuff crashes and burns. What I'm trying to say is: This also might affect "shiny" (i. Of course I can't guarantee that this problem also occured because of this bug, but I never had a clean install of Windows 10 fail so early. I tried to save a VirtualBox disk file inside the Cryptomator vault, and while the install was successful, Windows Update didn't work because of corrupted update files (at least that's what the hexadecimal error code translated to). I also think that it isn't just cp which is affected. Otherwise, I probably would've discovered this bug via an even more unfortunate way. But I diffed the actual and backup directory by pure chance, as I didn't touch this use case for some time. I've got a special use case where I copy a certain backup directory back and forth. Reproducibilityįirst of all, thanks a lot for fixing this bug, and so quickly to begin with! But do you have an estimate of when 1.6.9 is supposed to be released? I'm asking because this is one nasty bug, which might affect a lot of users without them even knowing ( yet!). The diff tool will note that binary files differ, and the hashsums will differ too. Using the "diff" tool should yield no changes at all. The files should be exact duplicates of each other. In lots of cases (but not always), the files will differ. Using the "diff" tool is usually enough, but hashsums also work. Simple example: "cp -a ~/vault/file.bin ~/vault/file.bin2" Do NOT use a higher-level application like the GNOME file explorer. Copy the file from its location in the vault into another location in the vault using the "cp" command.Copy a file, preferably a somewhat bigger (multiple MB) binary file, into the vault.Create a vault (located on Dropbox, but this shouldn't matter as the problem also happens if Dropbox is disabled). ![]() It seems to be a low-level problem which occurs if files get decrypted and encrypted at the same time? And it also seems to happen always for certain files, but intermittently for others. It is also important to use "cp", as other methods, like using the GNOME file explorer, work for whatever reason (which also means it is not a disk issue). This is important, as copying files into the vault from outside and copying files into the unencrypted filesystem from within the vault works perfectly. the files do not get copied to some other temporary destination in between. Copying within the vault means that the source and destination locations lie within the vault, i. This mostly (only?) seems to happen with binary files. I agree to follow this project's Code of Conductįiles get corrupted when they are copied within the Cryptomator vault using the "cp" command.I have searched existing issues for duplicates.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |