* updated travis-to-bintray upload config * Fixes cryptomator#825, fixes cryptomator#823 * create os-dependent buildkit.zip with all java resources required to build a self-contained package * moved ui control logic from initializer to setVault, removed readonly mode from windows * Updated SecPasswordField, which will now no longer store passwords in Strings but rather in char. * improved cleanup after unmounting and support for force-unmounting fuse volumes Probably already used by another volume." ( cryptomator#806) * improved logging in case of ": Mount failed: Cannot assign a drive letter or mount point. * Dokany-specific amendment for cryptomator#752 * Unlock vault with readonly flag if requested * Custom mount point now selected via Director圜hooser. * Delete automatically generated mount point after locking, attempt to fix cryptomator#773 * No longer assigning drive letters A-C to fix problems with older Dokany versions * updated IDE settings and removed duplicate gitignore * Repositioned messageText in unlock, updated "" copy * changing displayed message when no mount path given * reverting renaming of Properties concerning the usage of own mount point (rescheduled for 1.5.0) * Simplify mountPathProperty and implement its usage * adding input/output for the new custom mount points * changing naming of individual mout path property * Feature/custom mount point generalizing ( cryptomator#797) * Hide "check for updates" indicator by default * Added a Cancel button to the graceful shutdown-dialog. * attempting to downgrade to oracle jdk 9 because of stupid jdk 10 deprecationįixes cryptomator#742, fixes cryptomator#705 * changing description of own mount point usage * fixing ui bug: setting fields did not disappeared with mount adapter change * Add read-only option to the advanced settings * Next attempt to provide a solution for cryptomator#656. * tmp fix from cryptomator#29 apparently no longer needed with latest JDK. * attempt to correctly size the UI ( cryptomator#656) * As per feedback on PR cryptomator#690: refactored if-statement. * As per feedback on PR cryptomator#690: redid line wrapping, refactored signature for dialog builder method to include a default button, and the default button for the graceful shutdown dialog is now 'Force shutdown'. * now publishing ant-kit to bintray instead of github releases * jdk_switcher no longer needed, since codacy-coverage-reporter should now support jdk 10 (see codacy/codacy-coverage-reporter#83) * refactoring inconsistent method in vault class * small ui fix: text for using individual mount path is not shown completely I just installed the latest cryptomator 1.4.2 which seems to use dokany 1.1.1 if I'm not wrong, however I still face the same behavior of a file being read-only when I directly save it to the mapped vault drive from my Outlook client. You mentioned that the bug is fixed in the dokany-library 1.1.1 and I was wondering if it's possible to replace the library used by my current Windows installation with the fixed version of the dokany-library in order to fix the problem. Cryptofs is the core library of Cryptomator ( Is there going to be a permanent fix?Ĭan we switch out this library for our windows installations of cryptomator manually? However for every newly added file I (obviously) have the same problem again. Thank you, that helped as a workaround (I had to lock/close the vault first though). This command will remove from every file in the specified path and its subdirectories the "write protection" attribute. Enter the command `attrib -R /S "D:\path\to\secret\vault"` and hit enter. The log file has quite a lot in it just from the one delete action when in debug mode.Ģ. I have also closed FreeFileSync completely and there is currently no syncing to a cloud service. getFileInformation(): Invalid handle to /Finance/Quickbooks/AJPI_tmp. I now have six temporary files because I retried syncing several times. I then tried to delete the whole containing folder, but that also reappears. I tried closing the vault and re-opening without success. When trying to manually delete these files from File Explorer, they disappear then reappear when the screen is refreshed. (You can check the version in the Cryptomator settings.) DescriptionĪfter using FreeFileSync to sync files from hard disk to the Cryptomator vault, I saw that two temporary FFS files couldn't be deleted from the vault. I'm running Cryptomator in version: 1.4.0 I'm using Windows Pro 64 bit in version: 1803 searched existing (and closed) issues:.Before creating a new issue make sure that you
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |