The remaining open points of this ticket will be "won't fix" for now. When we plan to change something here, we should open new tickets, this one got confusing.

Sound sensible. Ok, then this ticket will only revert T8022 for archives which were renamed.

1. That the users focus on the documentation which is more important for them.
2. That the menu is not too long. This point will be +/- moot now but removing "more documentation" now would make extra work.

And 1) stays valid. So I'd keep it in place until all the new documentation is available. Unless @ikloecker sees this differently

Please keep in mind, that for the 3.4 release, we will most likely only have the User Manual ready, not sure about the Administrator Manual.

added vsd34 for the resetting of the defaults

In vsd 3.3.6 the option is now greyed out.

@ikloecker I'd like it if we could backport the resetting of the preferences to vsd34.

Font selection dialog lets the user choose a font size, which is then not respected - can we disable selecting the font size?

Any further improvements will have to go in a new ticket when we have a plan. I'll close this one.

ok, lets go with the message box.

Q1 stays like it is, for Q3 @tfry made a merge request to wrap after 120 characters. Please add a link to this.

Follow up for Q1 is T8166: Kleopatra: Add "Save Secret Team Key" button to success message after creation of "Team Key"

why gpg 2.4? Don't you mean 2.6? I'll add the proper 2.6 tag for avoiding confusion

FYI: We had a VSD support case today where the user complained that they thought the Admin PIN would work because of the tooltip text but it was not accepted. They needed to give the PUK, which is consistent with the state given in this ticket.

From the support angle, the worst of these issues is that the default will not be restored for VS-NfD. But then: nobody has inquired about that yet…

What is fixed, what needs still needs to be done and should go into another ticket?

I thought Gniibe's comment meant that gpg does report the errors now correctly…
So what is still to be done in gpg?

It is not (easily) possible to check for available keys first, before asking for a passphrase? (Like it is with gpg 2.2.)

I've created the ticket above for Q2, we need to discuss how to follow up Q1 and Q3 next week.

as T8022 was backported, this one should be backported, too, if possible. I'll add the tag

So this is all done, then. As for the open issue there is T7565: Kleopatra: Add tooltips in sign/encrypt window if an encryption type is greyed out

I guess those things need to be changed in Kleopatra after @gniibe made the changes in scd. I'll add a Kleo tag for discussion, as we should probably make several tickets from this.

I've made the above ticket for Q2. Regarding Q3 we leave it as is, if customers should complain we could then consider changing that.
Regarding Q1: we should talk about that next week. But I'll close this ticket.

Is this still a requirement?

well, you are showing 4 pinentry-qt windows above. The reference to pinentry meant those windows.

For verification text improvements we have various other tickets, see T8095. I'll add this one as another of those.

@ikloecker said (paraphrased by me):

@ikloecker said (paraphrased by me):

The case above shows the case where the public key for the imported secret key was in the keyring beforehand.
We'll assume that this is something which would probably not occur in real life and don't explicitly handle this.

So I'll set this to resolved.

Regarding the order of items on the page: It is basically the same order, but the frame for the encryption settings improves the overview.

Tested with Gpg4win-5.0.2-beta2

This is the dialog window which comes up when importing a team key with the group flag:

tested with Gpg4win-5.0.2-beta2

it was zsh

with Gpg4win-5.0.2-beta2:

Works with Gpg4win-5.0.2-beta2

@werner said the reading order should be like on the page https://gnupg.com/vsd/kleopatra-settings.html:

Tested with Gpg4win 5.0.2 (Beta):
Registry settings SOFTWARE\Gpg4win\Kleopatra\<config group>\<config entry>
works (I used [CertificateCreationWizard] EMAIL_placeholder for testing)

Ok in Gpg4win 5.0.2. (Beta), in German: