Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve change password workflow #621

Closed
tobihagemann opened this issue Jan 8, 2018 · 2 comments
Closed

Improve change password workflow #621

tobihagemann opened this issue Jan 8, 2018 · 2 comments
Labels
type:enhancement Improvements on an existing feature
Milestone

Comments

@tobihagemann
Copy link
Member

First of all, I want to know: Is it even necessary that the password can only be changed while the vault is locked? What was the design decision behind this back then?

If it's not necessary, should we just remove the restriction in DirectoryListCell.java#L98? And then also enable/disable "Remove from List" from the context menu while the vault is unlocked/locked.

@tobihagemann tobihagemann added the type:enhancement Improvements on an existing feature label Jan 8, 2018
@overheadhunter
Copy link
Member

overheadhunter commented Jan 8, 2018

Is it even necessary that the password can only be changed while the vault is locked?

Technically: No, not at all.

What was the design decision behind this back then?

There are two use cases:

  1. The user changes the password and unlocks the vault.
  2. The user changes the password and doesn't unlock the vault (immediately).

The latter one becomes more likely when changing password is possible while unlocked. Not using the password immediately makes it more likely to forget it. Thats all.

In any case it will be possible to restore the masterkey backup file, if unlock with the new password "doesn't work" (even though the user is 100% certain he entered the correct password^^).

@stale
Copy link

stale bot commented Jun 17, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Jun 17, 2018
@stale stale bot closed this as completed Jun 24, 2018
@infeo infeo reopened this Sep 3, 2018
@stale stale bot removed the state:stale Issues without any activity that will be closed automatically label Sep 3, 2018
@infeo infeo added this to the Backlog milestone Sep 3, 2018
@overheadhunter overheadhunter mentioned this issue Feb 22, 2019
6 tasks
@overheadhunter overheadhunter modified the milestones: Backlog, 1.5.0 Apr 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement Improvements on an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants