Rename masterkey file to prevent attackers from deleting it

[overheadhunter]

@TowerBR

However I have seen some requests here and on Github about the possibility of choosing the location of the masterkey file, some people even labeling it as a two-factor authentication (the second factor being the fact that you “have” the masterkey file). I understand the difficulties with mobile/sync.

Perhaps what solves all this is the possibility for advanced users to change this setting (the location), which would not affect basic users who would not even change it.

Giving users this flexibility is certainly the best option to satisfy most use cases. I guess you refer to discussions like this:

Using masterkey.cryptomator for 2-factor authentication

Reading about the way the masterkey.cryptomator file works, I thought it could be used to implement some sort of 2-factor authentication mechanism. Basically, if one didn’t sync the masterkey file on the cloud space where the rest of the files are, an attacker gaining access to the cloud storage would both have to KNOW the password and OWN the masterkey file through other means. The masterkey file could even be kept in sync with another storage space using another app which in turn only keeps …

We are in the process of refactoring some code related to key entry, which will also allow external key management solutions. Once rolled out, this will also enable things like FIDO. That said, we need a new vault format which supports storing required metadata.