Open GoogleCodeExporter opened 9 years ago
This can be deeply frustrating if you forget to save and then create a new
account with a strong password that you can't then log into.
The correct behaviour seems to me to be to store a temporary entry as soon as
the user moves away from keepassdroid (and regularly during editing). When the
user unlocks, if that entry is present then it should be reloaded.
The slight danger would be if the keepass file was edited outside keepassdroid
and the entry updated separately; this could be okay if a timestamp is stored
somewhere and the old entry is only overwritten if the timestamp is the same
age as the last write to the password file.
A related *really nice* behavior would be to have a temporary before and after
for when someone is doing a password change.
Original comment by mike...@gmail.com
on 19 Apr 2014 at 7:26
Original issue reported on code.google.com by
e...@esmithy.net
on 3 Dec 2013 at 5:39