Today
Done and backported for VSD 3.4.
So ok, go ahead Ingo with your plan in https://dev.gnupg.org/T7502#213972
I tend to agree with keeping it short and close to the wording we use for normal public key imports.
Yesterday
Backported for VSD 3.4
We decided to backport to VSD 3.4 because it fixes an accessibility issue.
Backported for VSD 3.4
We decided to backport to VSD 3.4 because it fixes an accessibility issue (wrong tab order).
Tue, Feb 24
Backported for VSD 3.4
Done.
How about "Certification includes that you check the fingerprint against a trusted source."? "Means" seems wrong to me. @hej, please comment
ok, lets do this. I'll update the description
I'm fine with just dropping it.
One doesn't even need a global config file to reproduce the duplication.
I'm okay with omitting the list of suggestions for shared secret keys. The person distributing the key should have told the recipients how to import and certify them properly.
Also backported for VSD 3.4.
Now also available in Gpg4win 5.
Mon, Feb 23
How about changing the text after sentence two simply to:
Do we agree to drop bolt font for QES certificates?
Will we change this for VSD 3.4?
Thu, Feb 19
Backported for VSD 3.4
For all tables where the visible columns can be configured via the context menu of the table header the visible columns can now also be configured via the context menu of the table cells/rows. (The only exception is the result table in the selftest where it doesn't really make sense to change the visible columns. Instead we should disable the context menu of the table header.)
Wed, Feb 18
Fri, Feb 13
Has now been backported to be released with 2.2.53
