If you mistakenly give a fingerprint of a primary key instead of a subkey fingerprint for encryption to the configuration option default-new-key-adsk and try to create a new keypair in Kleopatra, you get a general error:
We need a specific error for that instead of the general one.
Gpg reports "invalid ADSK specified".
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Testing | • TobiasFella | T6874 Kleopatra subkey management improvements | ||
| Testing | • TobiasFella | T6879 Kleopatra: Add support for adding an ADSK | ||
| Testing | None | T6882 Make ADSK configurable for new keys | ||
| Open | None | T7322 Kleopatra: General error if ADSK is not configured correctly |
Yes, gpg logs "invalid ADSK ... specified", but it doesn't emit a status error. This needs to be changed in gpg.