Please provide contradicting information if you have some, but the specialized security information sites would be awash with click-bait articles if such event happened even once. Since then, how many pieces of malware have been released which successfully attacked Kee Pass ?Īs far as I know, zero.
Theory is fine and dandy, but a reality check is called for. However, again, you need to be realistic. Use a proper firewall, only run software from trusted sources, do not open unknown e-mail attachments, etc. The only way to discover this spyware is to use a program that the spyware does not know about or cannot manipulate (secure desktop) in any case it cannot be KeePass.įor protecting your PC, we recommend using an anti-virus software. All interactions (like entering a password for decrypting the configuration, etc.) can be simulated.
This is law #1 of the Ten Immutable Laws of Security (Microsoft TechNet article see also the Microsoft TechNet article Revisiting the 10 Immutable Laws of Security, Part 1): "If a bad guy can persuade you to run his program on your computer, it's not your computer anymore".įor example, consider the following very simple spyware specialized for KeePass: an application that waits for KeePass to be started, then hides the started application and imitates KeePass itself. In this situation, the best security features will fail. In all the questions above we are assuming that there is a spyware program running on the system that is specialized on attacking KeePass. So no, using Kee Pass is much, much safer than using the password manager of your browser. it overwrites these memory areas before releasing them. This means that even if you would dump the KeePass process memory to disk, you could not find any sensitive data.įurthermore, KeePass erases all security-critical memory (if possible) when it is not needed anymore, i.e. While KeePass is running, sensitive data is stored encryptedly in the process memory. The database file itself is encrypted at all times, and even the data which is in memory is encrypted most of the time : Just read the security section of the help, where the developer envisions possible attacks.
0 kommentar(er)
