If you try to access multiple passwords within the wallet timeout, the latest version asks for the password every time it tries to access the wallet even though it is not closed yet. This occurs since 5.2.0 - 0.5.3 is not affected Reproducible: Always Steps to Reproduce: 1. Save some encrypted ssh keys 2. Save the corresponding passwords in kwallet 3. Try to load all the keys at once with "ssh-add ~/.ssh/*" Actual Results: One kwallet popup per key Expected Results: One kwallet popup for all keys, since they are imported within the wallet timeout
For me the new ksshaskpass does not work at all: It triggers kwallet passwort, but opening the wallte does not succeed at all. It only return a read error (error -9) Eberything fine with Version 0.5.3 though.
Marc, could be related to bug 343718.
Maybe, yes. One problem is, that many users now have two different kwalletd's running (old and new implementation) because they use a mixture of "old" qt4-based and new qt5-based applications. But the user is only able to manage passwords for the kwalletd for which the kwalletmanager is installed. And this can only be the old one (qt4-based) or the new one (qt5-based), not both. There seems to be no sane migration path in KDE. I saw myself up- and downgrading kwalletmanager several times to manage passwords. I know that the new kwalletmanager will migrate passwords to the new locations if the migration flag in its cnfig is not yet set. BUT the problem is, that many applications still use the old implementation and update/delete/insert passwords using the old kwalletd, so the already migrated data in the new implementation will be outdated very soon. This seem to be a very confusing situation for many users because propably you never know where your passwords and credentials will end up: new or old implementation? And you always have to provide a password for both implementations. And if you used different passwords in eacht kwalletd you always have to guess for which one it asks you this time. I think some sort of proxy-kwalletd for qt4-based applications should replace the old kwalletd so that there is only one place, where passwords will be stored. Or am I missing something here?
@Marc You are right. BUT if you have both wallets encrypted with the same password you should be asked two times (qt4 and qt5 version) and not again until the wallet times out. Right? For sshaskpass (which uses the qt5 implementation afaik) this does not work. It seems to close the wallet immediately and asks for every access within seconds.
I can confirm this behavior. I have both walletds running (v4 and v5). kwalletmanager is the v4 manager. Back in the days of »v4 only« ksshaskpass was leaving the wallet open. This means that once I had typed my password I could use ksshkaskpass as often as I wanted to without any further prompts. As I'm not only using this for ssh keys but other things as well (e.g. retrieving my mail account password for mutt, retrieving the password for several scripts) this was great. Now with ksshaskpass v5 I get prompted for my v5 wallet password each time ksshaskpass is executed. This is highly annoying.
Frederik, can you still reproduce it?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!