Find mount point of revealed vault using FUSE in Terminal on macOS High Sierra

os:mac

#1

I am new user and, after some research, it seems that all my problems using Cryptomator could be solved by an answer to the basic question indicated above. The details are as follows.

System: macOS High Sierra (10.13.6), FUSE 3.8.2, Cryptomator (1.4.0)
[Optional support for MacFUSE (?) selected on installation.]

Expected behaviour: After unlocking and revealing the vault with preferred volume type fuse, there is a directory “/Volumes/name_of_vault” to be found via Terminal.

Actual behaviour: No such directory appears (even though it does in Finder).

Attempted solutions:

  1. Set the preferred volume type to WedDAV. As a result, the directory “Volumes/name_of_vault” is created in the above process. However, it is not a solution for me, as I need to use “VIM - Vi IMproved 8.0” on the files in the revealed vault and thus run into the High Sierra unmount bug, see https://community.cryptomator.org/t/connecting-drive-failed-virtual-volume-dis-mounts-randomly/2324 and https://community.cryptomator.org/t/mac-os-x-high-sierra-unmount-bug/852.
  2. Choosing a custom mount point: this created a cascade of errors of various types depending on which mount point I chose; no success in getting a directory “name_of_vault” usable in the Terminal. If it is considered useful, I will try document these problems.

Question: How can I proceed, so that I have access to the files via Terminal and VIM?


#2

Install FUSE for Mac and under Cryptomator’s “Preferred Volume Type”, choose “FUSE”.

Backup your files to temp beforehand just in case.


#3

Thank you for your reply.

As I said in my original post, using FUSE - as you suggest - was my initial setup which raised the question mentioned in the last line of my post. I admit it is very basic; yet, I would be grateful for an answer to it.

Due to your recent answer to the post https://community.cryptomator.org/t/automatic-mount-monitor-script-for-macos/2329/2 of tobihagemann, I realise that the above-mentioned High Sierra unmount bug is fixed in Mojave. At the present stage, I would still prefer a smaller scale solution as upgrading the OS might have undesired side effects.