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
Revisions and Commits
rG GnuPG | |||
rG6c58694a885b gpg: Allow the use of an ADSK subkey as ADSK subkey. | |||
rG794950ec755e gpg: Allow the use of an ADSK subkey as ADSK subkey. | |||
rGd30e34569244 gpg: Allow the use of an ADSK subkey as ADSK subkey. | |||
rGf1e1cb0767a1 gpgconf: Allow listing of some new options | |||
rGecda4b1e1694 gpg: Add magic parameter "default" to --quick-add-adsk. | |||
rGeafe17532069 gpg: New option --default-new-key-adsk and "addadsk" for edit-key. | |||
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 | ||
---|---|---|---|---|
Testing | • TobiasFella | T6874 Kleopatra subkey management improvements | ||
Testing | • TobiasFella | T6879 Kleopatra: Add support for adding an ADSK | ||
Resolved | • werner | T6882 Make ADSK configurable for new keys | ||
Open | • werner | T7313 gpgconf --list-options does not handle multiple trusted-keys. | ||
Testing | None | T7322 Kleopatra: General error if ADSK is not configured correctly |
Event Timeline
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.
Now also with support for --quick-add-adsk in 2.6. This will work also for gpgme without further changes.
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.
Status is testing for 2.4, no backport yet for 2.2, so there it stays in the backlog column
werner: Can you also backport listing of "default-new-key-adsk" with gpgconf so that Kleopatra can check whether a default ADSK is set?
Done for 2.2. It is already in 2.4.
While testing this I noticed that only the last adsk or trusted key is listed. Thus several assurances of this options are not properly represented. See T7313