Reqeust: Currently KeePass locks the database after x seconds or alternatively
closes the program.
There could be an option to close database x seconds after it has been
locked.
If the database was opened and has been locked it can be expected that the
user wants to use it again, but if he/she doesn't use it in x seconds (lets
say 1200) the database will be closed.
Reply: sender: pail459
What is the difference between closed and locked? How do you see this being
used?
p.s. please post these in Open Discussion first, it is easier to discuss
there.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> Locked: The database is locked. The user needs to type the masterpassword only.
> Closed: The database needs to be loaded again, then the masterpassword is entered.
KeePass also closes the database when locking. This is mentioned on [1]. When locking, KeePass closes the file and erases all memory, i.e. the database also needs to be loaded from disk after locking. The only difference between locking and closing is that when locking, KeePass additionally remembers the last view settings (last opened group, top visible entry, etc.), of which none is security-critical.
The only thing is that everybody can see the locked database. Nobody can access it. (Until the password isn't weak. Or AES is broken) If the database is closed nobody knows which database was open, because the title of it isn't shown. If nobody knows which database is the desired one he will have to crack every one.
If this doesn't fit in your policy or if this isn't your cup of tea you could make KeePass close X seconds after the database has been locked. Has the same effect.
Thank you for discussion.
Regards,
bastik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I moved that from there: http://sourceforge.net/tracker/index.php?func=detail&aid=2579642&group_id=95013&atid=609911
Reqeust: Currently KeePass locks the database after x seconds or alternatively
closes the program.
There could be an option to close database x seconds after it has been
locked.
If the database was opened and has been locked it can be expected that the
user wants to use it again, but if he/she doesn't use it in x seconds (lets
say 1200) the database will be closed.
Reply: sender: pail459
What is the difference between closed and locked? How do you see this being
used?
p.s. please post these in Open Discussion first, it is easier to discuss
there.
cheers, Paul
Locked: The database is locked. The user needs to type the masterpassword only.
Closed: The database needs to be loaded again, then the masterpassword is entered.
The order is kept. Database unused... locked.... still unused... database closed. (or KeePass) If this accepted and not considered as unnecessary.
BTW: I requested two more things that haven't been commented yet.
What is the advantage? The database is secure open or closed. An opened database is only copied to memory, not disk.
cheers, Paul
> Locked: The database is locked. The user needs to type the masterpassword only.
> Closed: The database needs to be loaded again, then the masterpassword is entered.
KeePass also closes the database when locking. This is mentioned on [1]. When locking, KeePass closes the file and erases all memory, i.e. the database also needs to be loaded from disk after locking. The only difference between locking and closing is that when locking, KeePass additionally remembers the last view settings (last opened group, top visible entry, etc.), of which none is security-critical.
Best regards
Dominik
[1] http://keepass.info/help/base/security.html#seclocking
The only thing is that everybody can see the locked database. Nobody can access it. (Until the password isn't weak. Or AES is broken) If the database is closed nobody knows which database was open, because the title of it isn't shown. If nobody knows which database is the desired one he will have to crack every one.
If this doesn't fit in your policy or if this isn't your cup of tea you could make KeePass close X seconds after the database has been locked. Has the same effect.
Thank you for discussion.
Regards,
bastik