I had an issue this morning with a Cryptomator Windows client. The client is set up to start at boot and unlock the vaults mounting them as a drive letter, which works totally fine opening the client manually while windows is already running. If I go through a full reboot though, it seems I run into a minor issue with the automatic unlock/mounting.
The device is set with permanent (killer switch) setting so no Internet connectivity is available until the VPN is fully established.This means that the morning log-in process will go through:
- Wait until the VPN boots up
- Delayed MEGA cloud client opening (MEGA client would do this by default)
- Cryptomator starting but it seems a bit too early
I would have though Cryptomator would take this scenario in mind and either allow for a delayed start or perform a Vault target-cloud reachability test before kick off.