#622 Consider replacing KGpg with Kleopatra
Closed: Fixed by siosm. Opened by tobiasfella.

My understanding is that Fedora KDE preinstalls KGpg (through the @kde-pim group).

KGpg is effectively unmaintained. From my limited testing, it's quite rough and doesn't offer many of the features kleopatra has. (e.g., it doesn't allow creating elliptic-curve keys or adding subkeys), and doesn't use normal gpg components (e.g., doesn't use a pinentry for entering the pin for a new key). IMO its main view is confusing for non-expert users, showing certificates, subkeys, user ids and signatures in a single tree view. It also offers some questionable features (e.g., it lets the user create an address book entry for a subkey or a signature, whatever that means)

Kleopatra is actively maintained by upstream gnupg and doesn't have these problems.

(For transparency, I'm paid to work on kleopatra)


Yes, let's do this. Kleopatra is so much better.

Metadata Update from @ngompa:
- Issue assigned to ngompa
- Issue set to the milestone: Fedora Linux 43
- Issue tagged with: easyfix, experience

Metadata Update from @ngompa:
- Issue tagged with: default-apps

Should we obsolete kgpg with kleopatra?

I've sent the pull request to update the default GPG app: https://pagure.io/fedora-comps/pull-request/1145

However, since it requires changes to OpenQA, I'm waiting until @adamwill or another member of Fedora QA gives me to all-clear.

I think this has been done with: https://pagure.io/fedora-comps/pull-request/1145

Metadata Update from @siosm:
- Issue close_status updated to: Fixed
- Issue set to the milestone: None (was: Fedora Linux 43)
- Issue status updated to: Closed (was: Open)

Metadata
Related Pull Requests