https://bugs.kde.org/show_bug.cgi?id=505596
--- Comment #33 from Terry Coles <[email protected]> --- (In reply to michaelk83 from comment #32) > Specifically with KWalletManager, there's an intentional password hint that > tells Klipper that this is sensitive information. See bug 156547. > However, Klipper could handle that hint better, in a way that's less > confusing to the user. Or offer a configuration choice. I don't know if a > separate request for that has been posted. I didn't find one. Right so this behaviour was added after a request in that bug report. I'm think I understand why but I'm not sure I understand how to work with it. Ever since I started using KWalletManager (probably getting on for 20 years ago now), I've used it as a secure repository for my passwords and other sensitive and / or easily forgotten information. I have to say, I've never really understood any other way to get the password from the wallet to the browser (maybe it worked with Konquerer in the early days, but most of us now use Chrome or Firefox). I now use another password manager, which allows the password to be copied directly to the browser when needed (not Chrome, but another more secure type). However, I am still populating that manager with my hundreds of different credentials that I have built up over the years and my source for this was KWalletManager. Until this change, I could simply paste the credentials into the browser and then save them to the manager. Now this no longer works, I have to paste the credentials into Kate, so that I can then copy them into the browser. Apart from baffling me for many months, I'm not convinced that the security is improved. BTW. This may be the wrong place to ask this question, but if KWalletManager / Klipper prevent credentials being copied, what is the purpose of KWalletManager? -- You are receiving this mail because: You are watching all bug changes.
