Bug 348560

Summary:	KWalletManager should allow GPG key migration
Product:	[Applications] kwalletmanager	Reporter:	Valentin Rusu <valir>
Component:	general	Assignee:	Valentin Rusu <valir>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	bjoernv, borden_c, bugs, heri+kde, livier, mk.mateng
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Valentin Rusu 2015-06-01 21:42:30 UTC

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

Comment 1 livier 2018-06-04 23:57:52 UTC

+1

Comment 2 bjoernv 2019-05-13 20:28:47 UTC

*** This bug has been confirmed by popular vote. ***

Comment 3 bjoernv 2019-05-13 20:37:54 UTC

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

Comment 4 Borden 2019-05-13 22:29:41 UTC

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.

Comment 5 michaelk83 2022-09-06 10:05:47 UTC

(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).