Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1175 Locking does not work when Edit Entry dialog is open

KeePass_2.x
closed
nobody
5
2013-10-25
2013-10-21
LabanO
No

Hello,

The workspace never locks if you have the Edit Entry dialog open.

I know this issue has been reported before:
https://sourceforge.net/p/keepass/bugs/1115/

And I have read this:
http://keepass.info/help/base/faq_tech.html#noautolock

So the main issue is what to do with unsaved data in the Edit Entry form.

However, since having the password database unlocked indefinitely just because a dialog box is open is obviously a bad thing from a security point of view, I have a couple of suggestions that might alleviate the issue:
1) If there are no unsaved changes, just go ahead and lock the workspace. Not need to worry about saving, since there are no unsaved changes.
2) Add an auto-save feature (option) so that when you exit the Edit Entry form with Ok, it always saves the changes. The same with new entries. With this in place, any time you enter the Edit Entry form there should be no other unsaved changes than the ones you might make in this form. This should make #1 above work a lot better, since there will more rarely be unsaved changes to prevent locking.
3) Maybe even add an option to always lock the workspace even though it will result in unsaved data being lost (with the proper warnings next to this option). It will then be the user's choice whether or not to use this feature.

Related

Bugs: #1175

Discussion

  • Paul
    Paul
    2013-10-22

    Please don't post on this topic under bugs. We are happy to have the discussion in the "normal" forums.

    1. You can do this with a trigger.

    cheers, Paul

     
  • Dominik Reichl
    Dominik Reichl
    2013-10-22

    • status: open --> closed
    • Priority: 7 --> 5
     
  • LabanO
    LabanO
    2013-10-22

    Paul,

    Sorry, my bad.

    I just saw the other two very similar feature requests, and I have added a
    comment to one of those.

    Is there anything else that I could do that might get this addressed?

    Lars

    On Tue, Oct 22, 2013 at 8:01 AM, Paul pail459@users.sf.net wrote:

    Please don't post on this topic under bugs. We are happy to have the
    discussion in the "normal" forums.

    1. You can do this with a trigger.

    cheers, Paul

    Status: open
    Labels: timeout lock
    Created: Mon Oct 21, 2013 10:18 PM UTC by LabanO
    Last Updated: Mon Oct 21, 2013 10:18 PM UTC
    Owner: nobody

    Hello,

    The workspace never locks if you have the Edit Entry dialog open.

    I know this issue has been reported before:
    https://sourceforge.net/p/keepass/bugs/1115/

    And I have read this:
    http://keepass.info/help/base/faq_tech.html#noautolock

    So the main issue is what to do with unsaved data in the Edit Entry form.

    However, since having the password database unlocked indefinitely just
    because a dialog box is open is obviously a bad thing from a security point
    of view, I have a couple of suggestions that might alleviate the issue:
    1) If there are no unsaved changes, just go ahead and lock the workspace.
    Not need to worry about saving, since there are no unsaved changes.
    2) Add an auto-save feature (option) so that when you exit the Edit Entry
    form with Ok, it always saves the changes. The same with new entries. With
    this in place, any time you enter the Edit Entry form there should be no
    other unsaved changes than the ones you might make in this form. This
    should make #1 above work a lot better, since there will more rarely be
    unsaved changes to prevent locking.
    3) Maybe even add an option to always lock the workspace even though it
    will result in unsaved data being lost (with the proper warnings next to
    this option). It will then be the user's choice whether or not to use this
    feature.


    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/keepass/bugs/1175/

    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/

     

    Related

    Bugs: #1175

  • Paul
    Paul
    2013-10-25

    My answer should have been: 2. You can do this with a trigger.

    I must have made a typo. ;-))

    cheers, Paul