https://bugs.kde.org/show_bug.cgi?id=385984
--- Comment #1 from Ivan Čukić <ivan.cu...@kde.org> --- > What took me by surprise is that limiting a vault to an activity > will actively attempt to close the vault when you go to another one. > I don't see the point of that. The problem with full-device encryption is that once you log in, everything is accessible to people who have access to your system. Vaults are meant to be smaller containers that should be open for as short as possible. When you switch to another activity, this implies you stopped working on the project you worked on in the previous activity, and the vault automatically closes to minimize the time it is kept open. Having to manually close a vault is problematic for forgetful users (myself included). If it is not possible to close it (an application is using it), you get a notification with an option to kill the applications and forcefully close the vault. Automatic closing will also be implemented for when the screen locker is started, and similar situations. As far as the recent documents are concerned, the files belonging to a vault will not be tracked in future at all (like the "Baloo" issue). We do not have the infrastructure to have distributed databases for usage statistics and text indexing to allow "chunks" of the database to be stored in a separate file located in an encrypted directory. -- You are receiving this mail because: You are watching all bug changes.
