Summary: | kwallet has no way of preventing access to data if a wallet is open | ||
---|---|---|---|
Product: | [Applications] kwalletmanager | Reporter: | bonne |
Component: | general | Assignee: | George Staikos <staikos> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
bonne
2005-10-24 17:40:27 UTC
Sorry, those are both technically impossible. There is no way to prevent some application or tool from pretending to be another application. As much as we might want to see that happen... Are you saying I'm better off just not using kwallet at all? It would seem to me to be more secure to have a password partially obscured in some text file than open for all to see with an inviting wallet icon. On Monday 24 October 2005 19:31, Bonne Eggleston wrote:
> 2005-10-25 01:31 ------- Are you saying I'm better off just not using
> kwallet at all?
> It would seem to me to be more secure to have a password partially obscured
> in some text file than open for all to see with an inviting wallet icon.
No, I'm saying that we can't provide any guarantees of which application
we're talking to, so there's no point in layering on code that doesn't help.
If you're worried about the icon, hide it, or remove/rename kwalletmanager.
You can also do the secure thing and simply set a timeout to automatically
close the wallet.
What is being asked here is to prompt once more for the wallet password once the "read password in clear text" feature is being accessed. This is easy, not impossible... To make things worse, you can change a wallet's master password without providing the old master password! (if the wallet is open, that is, but that's the whole problem :)) |