cryptomator / cryptomator/cryptomator
Option to start two instances of Cryptomator with different privileges (Windows)
- Dominant language
- Java
- Stars
- 16.1k
- Forks
- 1.5k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 1
Description
### Summary
Dokany doesn't allow the FUSE mount option "allow_root" which would allow root/admin in addition to current user.
The consequence is that mounted Vaults are by default only accessible to current user, excluding administrator users.
Any application or service needing admin privileges for some tasks (files access, Shadow Copy VSS service for backup...) cannot access the mounted vault if the user is logged in under his own user name, even if the user profile has administrator privileges.
The only current option is to use custom mount flags in Cryptomator and remove the "--options CURRENT_SESSION" flag. The side effect is that any logged in user will have access to the mounted vault.
### Motivation
- be able to log in to windows as a user and not necessarily as an administrator for security considerations
- be able to perform tasks needing administrator privileges on the mounted vaults without exposing the vaults to all users
### Considered Alternatives
- Dokany doesn't allow this in its source code (would be the simplest approach)
- One option would be to be able to start more than one instance of cryptomator :
Each instance can be run under its own privileges.
An alternative is to have a core Cryptomator service with system privileges. Different instances of user GUI can then be started by each logged in user. The User GUI ensures a Dokany service with user rights access. The core service ensures a Dokany service with administrator privileges.
### Additional Context
Administrator would have access to the contents of a mounted vault by any user.
User could allow or not access to administrator in the GUI (but not sure if it is feasible!)
Contributor guide
Assessment
This issue has not been assessed yet.