Feature: Autolock

[overheadhunter]

In the unlock screen, there should be the option to unlock a vault only for a certain amount of time. E.g. by using a SplitMenuButton (same as the "Lock" button) and offer some predefined time periods such as "Unlock for 30 Minutes".

[tobihagemann]

Is it feasible to offer this only with inactivity? Similar to a screen saver. Not sure how this will impact performance, but activity could be measured by "is the filesystem accessing the drive".

[overheadhunter]

Ack. Filesystem I/O activity is measured anyway and doesn't influence performance.

[RiseT]

I'd like to add:

Optional vault auto-locking when...

• the OS's lock screen comes up
• system switches into Sleep or Hibernate mode

[overheadhunter]

Might be of interest: com.apple.eawt.AppEvent.ScreenSleepEvent.

[Riajyuu]

I want #6 a bit more: auto lock after certain time of inactivity.
But for this app, it is not a password manager or sth like that.
So this feature is not that urgent tough useful in some cases.

[pascalandy]

+1
I keep forgetting about it.

This will be the perfect setup along using Bitwarden :-p

[Quameda]

+1

[DimiTech]

This would be an awesome thing to have 👍

[t4087]

I really would like to see this. Or even closing the app via powershell script without force closing it would be nice (for the purpose of locking). Tbh, even having the "lock" button seems archaic. Ppl be lazy. Where the app is a security tool, it really would be amazing. If you prefer to add it as a "donate to use" feature like dark mode? I'm on board. As long as it isn't recurring. :) I've been looking to donate anyhow. Not that not having this feature will stop me from doing so, but I mean.... might happen sooner than later. Amazing app, thank you!

[samsaraswheel]

Was about to log a new one on this but saw this already open. Also for supporting this option.

Running Linux Mint 19.3
Cryptomator 1.5.4 appimage

My question is in the meantime...is there currently a command line option available to do a graceful unmount/shutdown of Cryptomator?

e.g. the similarity of ... cryptomator -shutdown -force or cryptomator -dismount

For the user purposes of doing a custom scheduled cron script or init.d graceful shutdown script in the interim.
Reason being I currently have lots of hs_err_pidxxxx error logs when normally shutting down the pc with a Cryptomator mount still open. But no problems with a manual unmount before hand. Will log later if needed on further investigation, could be just my system at this stage.

[infeo]

is there currently a command line option available to do a graceful unmount/shutdown of Cryptomator?

No. If you want to use the command line, look at cryptomator/cli.

[shaiguitar]

Bumping this one again too. If there's a PR in the works, and/or any direction of how this would be implemented, happy to take a stab at it. Specifically, I think on-sleep/hibernate is a good use-case of auto locking and one that I would definitely use.

[visnetje]

+1

[BeyerMart]

To summarize the requested Unlock Options:

1. Same behavior as before. (Do not lock while Cryptomator is running and Lock Vault is not performed)
2. Lock after x amount of minutes (ToDo decide hard cap 30 Minutes or user input)
3. Lock when the system goes into Sleep / Hibernate / System Lockscreen (Depending on used OS)

[BeyerMart]

I was also thinking about adding these locking functions not just on the unlock (a locked vault) screen, but also at the lock (an unlocked vault) screen.
So another SplitMenuButton like this:

[overheadhunter]

Just to discuss alternatives: Instead of "lock in x min", in everyday use "lock when idle for x min" might be more useful?

Also, we should find a better term that describes all of sleep, screen saver, OS lock screen, etc.

[tobihagemann]

Some inspiration from 1Password:

I think that auto-lock should be a "passive" setting. Making it an "active" setting (or action), you have to consider a lot more things: Can the "delayed" action be aborted? How do we see in which state the auto-lock is currently in?

[BeyerMart]

Thanks for your input.
With that, I created the following UI as a separate Tab in the Vault Options.

Obviously, the last two lines should be in one, as in @tobihagemann 's screenshot. I really like that.

But having the Textfield "in" the checkbox might be quite tricky.
One could put everything into an HBox like:

<HBox>
	<CheckBox text="%vaultOptions.autoLock.lockAfterIdleTime" fx:id="lockAfterIdleTimeCheckbox"/>
	<TextField fx:id="lockIdleTimeInMinutesTextField"/>
	<FormattedLabel format="minutes"/>
</HBox>

But I am not completely happy with this, as clicking on the latter "minutes" does not change the state of the checkbox.

Further development takes place in this branch

[overheadhunter]

But I am not completely happy with this, as clicking on the latter "minutes" does not change the state of the checkbox.

Maybe you can use <TextFlow> to encapsulate multiple elements that should be displayed in one line. This has already been used in other places like in the "Welcome" view:

cryptomator/main/ui/src/main/resources/fxml/vault_detail_welcome.fxml

Lines 17 to 21 in 2720a99

	<TextFlow styleClass="text-flow" prefWidth="-Infinity" visible="${controller.noVaultPresent}" managed="${controller.noVaultPresent}">
	<Text text="%main.vaultDetail.welcomeOnboarding"/>
	<Text text=" "/>
	<Hyperlink text="docs.cryptomator.org" styleClass="hyperlink-underline" onAction="#visitGettingStartedGuide"/>
	</TextFlow>

Keep in mind though, that this can be tricky during localization:

• "Lock when idle for [ ] minutes"
• "Nach [ ] Minuten Inaktivität sperren"

[BeyerMart]

To use the integrations-api correctly I was thinking of the cryptomator code first.
I would like to have one "SystemState" Listener instead of a solution per Vault.

With each change in the SystemState (Enum with ACTIVE, SLEEP, LOCKSCREEN, SCREENSAVER;) I will look at each vault and check if the respective Setting to the newSystemState is True

cryptomator/main/ui/src/main/java/org/cryptomator/ui/fxapp/FxApplication.java

Lines 217 to 228 in 8592e36

	private void systemInterfaceStateChanged(SystemState systemState) {
	vaultListManager.getVaultList().forEach(vault -> {
	switch (systemState) {
	case SLEEP -> {
	if (vault.getVaultSettings().lockOnSleep().get()) {
	try {
	vault.lock(true);
	} catch (Volume.VolumeException e) {
	e.printStackTrace();
	}
	}
	}

Does this look like a good approach? @overheadhunter

[BeyerMart]

For the SleepEvent I found this Listener Interface from awt, but do not think of using it.