Version: 1.1 (using 3.5.9, Kubuntu (hardy) 4:3.5.9-0ubuntu7.1) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.24-19-generic I want to store certain credentials in a separate wallet with a separate password. For example, my banking passwords and my yahoo mail passwords don't belong in the same place. I don't care about my yahoo password, but if I step away from my workstation, I don't want my coworkers to use my banking password. I don't want to have my banking password decrypted until the moment I use it. kwalletmanager doesn't seem to know that there is useful information in non-default wallets. It would be nice to have an option: * Which wallet do you want to add this to? * Move these credentials to another wallet Can it be done?
This is actually application-specific. KWallet allows any application to store its passwords in any wallet it likes. There's currently 2 predefined wallets: local and network wallets. The problem is konqueror which doesn't allow you to change the wallet you want to store a specific password in. Reassigning.
Hi Michael, thanks for having a look. All of the KDE applications use the default wallet. My difficulty is not which wallet the password gets put in, but that it must stay there. I would like to move it from one wallet to another. The application doesn't really need to know where the password is stored - simply that it is somewhere in the wallet system. The wallet system produces the password by asking the user if it is okay, decrypting the appropriate wallet, etc.
*** Bug 216824 has been marked as a duplicate of this bug. ***
(In reply to Duckworth Lewis from comment #2) > I would like to move it from one wallet to another. The application > doesn't really need to know where the password is stored This would be somewhat possible once everything migrates to Service Service. It has global search, which is independent of where things are stored. But it would still break if the client app uses `Collection.SearchItems()` instead of `Service.SearchItems()`.
But see also 228308 comment 14.
Oops, wrong link. Should be: Bug 228308 comment 14. Sorry for the multi-post noise.