Via the Gpg4win support channels, we had meanwhile two reports of people that tried to import only keys (probably pubkeys and secret keys) not working. It turned out to be ignored PGP-2 keys.
So I'd think it is a use case that during key-import, it is more clearly visible why a key import
did not work.
gpg: ASCII-Hülle: Version: GnuPG v1.4.9 (MingW32) - GPGshell v3.64
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg: ignorierte PGP-2 Schlüssel: 1
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA5e5257a94f40 Show skipped v3 keys in import result | |||
| rM GPGME | |||
| rMad95288d3b3e cpp: Expose skipped_v3_keys | |||
| rMa630a1e3e74c core: Parse skipped_v3_keys | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | • aheinecke | T3742 Gpg4win 3.1.0 | ||
| Resolved | • aheinecke | T3776 Indicate that and why PGP-2 pubkeys (or secret) keys are not imported |
Kleopatra now shows this:
Will be part of the next Gpg4win release.
For GNU/Linux it will likely take longer to get into distros as this needs a currently unreleased GPGME version.