When a first GPG-based wallet is created, it uses a user specified GPG key to encrypt the data. Later on, the user may want to revoke the old key and switch to a new one. Currently, there are no means to let users switch from the old key to a new one. KWalletManager should provide the means to perform this operation. Reproducible: Always
+1
*** This bug has been confirmed by popular vote. ***
Until the bug is fixed, the following work-around helps: * export wallet data as XML * backup ~/.local/share/kwalletd * delete the wallet * create a new wallet with a new GPG key * import XML data
Perhaps going forward KWallet should consider becoming a pass frontend? Pass handles key changes seamlessly and there are already a number of Qt frontends for it. It would be nice to have full pass-KDE integration, too.
(In reply to B Rhodes from comment #4) > Perhaps going forward KWallet should consider becoming a pass frontend? Pass > handles key changes seamlessly and there are already a number of Qt > frontends for it. It would be nice to have full pass-KDE integration, too. See Bug 399232 comment 4 (and 5).