#542 Close DB when locked

[Val Schuman]

I'd like to be able to close the DB when PS is locked. It's useful if one is using multiple databases or when the DB gets synched to a dropbox or something similar only when the DB is closed. It's inconvenient to have to unlock it first only to close it right after.

It's not a security issue either, I think, given that one can just end task PS and reopen it with a closed DB.

[DrK]

If you use the System Tray, you can right click on the icon there and select Close (as long as no Edit or Options dialog was open when it minimized to the System Tray).

David

[Val Schuman]

Aha! I had a dialog open when PS was locked. Should it still provide the option but remind the user that there's a dialog open? I don't think it would disclose anything another user wouldn't know, since "no close option" == "dialog left open"?

[DrK]

BTW - both the Close and Exit menu items are not available if a dialog is open when the database is locked. This is because we really can't guess as to what the user intends and, if locked, we would need to read the database again and then give the user the option of action.

I thought the Help file gave this information (I will ask for this to be there if not) but I don't think we can change this process at the moment.

David

[Dave C]

It would be useful if the Security option "Lock password database after x minutes idle" was either changed to "Close password database after x minutes", or you simply added one more option to "Close password database after y minutes".

I use dropbox to store the pwfile, and forgetting to close it makes for a mess. This would be extremely useful in this scenario.
Thanks for reconsidering.

[WvV]

I would like this option! We are with multiple users, using the same database over a network. When one user forgets to close the database (or pwsafe), the others can only open it read-only.

[chris134]

+1 for this option -- we use shared Dropbox folder to access pwsafe from multiple computers and phones. IF pwsafe automatically closed the database after a fixed/selectable timeframe - the frequency of times conflicted copie are created would be dramatically reduced. Dropbox is quite fast at syncing files, so if the first user makes an edit, then shortly thereafter pwsafe will close and the current pwsafe database will by synced across all Dropbox copies.

Often users need to quickly access a password, and once done, pwsafe is minimized but still running in the background for a long time.... which increases the risk of another user attempting to edit a pwsafe database and creating yet another confliced copy

[Marv]

Manage/options/system has a check box titled "Open database read-only by default". Would this not work if all PW clients were set to this option except one "master" client? The master client would be used to make all edits.