Nitrokey / Nitrokey/nitrokey-documentation

suggest use of Kleopatra for gui method to create and manage gpg keys instead of GPA

Open
#415 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
36
Forks
53
Avg merge
1d 16h
Merged PRs (30d)
5

Description

File: [components/nitrokeys/features/openpgp-card/openpgp-keygen-gpa.rst] https://docs.nitrokey.com/components/nitrokeys/features/openpgp-card/openpgp-keygen-gpa.html

I would suggest to recommend users to use kleopatra as a gui replacement for GPA. GPA seems to hardly have much development ,and the last stable binary most distro ships is 0.10.0 which was released 6years ago. I haven't checked on with the windows version as its bundled with gpg4win , but it probably shipping the older versions too.

Kleopatra is more actively developed (by kde) and supports smartcard functions along with a better ui and user experience.

Also if kleopatra is installed through flatpak it brings its own version of gpg , which is updated and more recent version of gpg , making things more secure.

Also for some reason GPA program does not recognise my nk3 and gives "card appplication not supported" wherease works perfectly with kleopatra.

making a guide with kleopatra shouldn't take much time too.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with components/nitrokeys/features/openpgp-card/openpgp-keygen-gpa.rst and compare it with the rendered page linked in the issue. Update the guide to recommend Kleopatra for creating and managing keys, preserving the relevant OpenPGP card guidance. Done means the documentation clearly presents Kleopatra as the replacement for GPA.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.