The correct way to tackle this is first analyzing your situation: in your case, you have a number of potential tools that you want to use. This cannot really work because, while everyone will agree on the "price" part, the balance between security and usability is specific to each case: I will not have the same requirement as you so while a specific choice might makes sense for me, it will not for you, for my father or for a coworker of mine. In your specific case, you're trying to offload that choice to "the community" (which, in itself, is a misnomer: "the community" doesn't exists any more than "the people" do). here is why:ĭesigning security is mostly about making choices between price, usability and security. ![]() That question is, unfortunately, mostly opinion-based. But what about the Kee 2.0 Firefox add-on and the RPC plugin? Do those pieces have the same level of security review? On the other hand, the community seems to view KeePass favorably. I assume LastPass has had much more extensive security review and probably has a team of trained professionals keeping the whole thing secure. However, my question centers on the question of to what extent does using the Firefox addon with KeePass expose the entire password database to Internet-based attacks (of any type, including phishing - anything that originated from outside).
0 Comments
Leave a Reply. |