The usecase for ADSK is mostly that in an organisation the Admistration will set an ADSK throgh the Windows registry for new keys. So T6879: Kleopatra: Add support for adding an ADSK is more of a fallback for existing keys. We should read that from the config when generating a new key, Similar to T6881: Kleopatra: Make designated revoker configurable for new keys and automatically add such a subkey for newly generated keys if it is configured.
Description
Description
Revisions and Commits
Revisions and Commits
| rG GnuPG | |||
| rG4d901904d7f6 gpgconf: Allow listing of some new options | |||
| rGdf977729ff38 gpgconf: Allow listing of some new options | |||
| rGce75af47eba8 gpg: Add magic parameter "default" to --quick-add-adsk. | |||
| rGc6cecbd89a76 gpg: New option --default-new-key-adsk. | |||
| rG77afc9ee1c75 gpg: Add magic parameter "default" to --quick-add-adsk. | |||
| rGed118e2ed521 gpg: New option --default-new-key-adsk. | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | TobiasFella | T6874 Kleopatra subkey management improvements | ||
| Testing | TobiasFella | T6879 Kleopatra: Add support for adding an ADSK | ||
| Open | None | T6882 Make ADSK configurable for new keys |
Event Timeline
Comment Actions
This should not be configured in Kleopatra but an option to gpg because this is a core crypto functionality. Thus is now a gpg task.
Comment Actions
Now also with support for --quick-add-adsk in 2.6. This will work also for gpgme without further changes.
Comment Actions
It would be helpful if gpgconf --list-options gpg listed the default-new-key-adsk option so that Kleopatra knows whether the option is set.