Fixed and backported for VSD 3.4

Backported for VSD 3.4

Backported for VSD 3.4

Backported for VSD 3.4

Fixed. When one of the lists/tables gets focus then NVDA should speak something like "<name of list> list" or "<name of table> tree view".

Note: QGpgMEWKDLookupJob uses an Assuan transaction with dirmngr.

We had considered and rejected adding below the above configuration a marked section (like e.g. with a frame) showing the options in the order they appear in the sign/encrypt window:

• Sign as
• Encrypt for me
• Encrypt for others
• Encrypt with password
• Encrypt / Sign each file separately

We discussed this and decided that this would not be useful, as

I'm fixing this issue under T7855. So, I move this ticket as a child of T7855.

@timegrid Thank you for your confirmation.

I can't reproduce this in vsd-3.3.90.19 @ win10 anymore.
Probably the fixes in https://dev.gnupg.org/T7827 or https://dev.gnupg.org/T7855 solved this, too.

This does not occur any more in Gpg4win-5.0.0-beta369

The latter is also the case for deleted softkeys.

Might be related to T7836?

The regression that the Welcome screen didn't go away after generating the very first key has been fixed. The fix has been backported for VSD 3.4 and VSD 3.3.

I was asked to test this again with a newer version. With Gpg4win-5.0.0-beta369 not much has changed, you still can choose "Certify" on the only secret key and the certify window only allows "Cancel". Difference is only that now the "Certify with" line is empty:

If a high-contrast mode is enabled then Gpg4win 4.4 (and VSD 3.4) will use the Fusion style which works much better with high contrast than the Windows XP/Vista style with animations that was used previously.

(writing this much later, since got lost)

I had a look at Qt 5. All of Qt's Windows styles are broken with regards to button or menu item styling. They change the background color of the hovered and/or selected button, but they use the default foreground color of the common base style class for the text. I don't think that fixing the (obsolete) Windows styles is worth the effort. As workaround we should use the Fusion style if high-contrast is active.

As this was finished more than a year ago, this should be included (and testable) in vsd

It was decided that we don't want to improve this in KConfig.

Tested a little late and on Windows 11 with VS-Desktop-3.3.90.16-Beta (a Beta for VSD 3.3.3):

Fixed and backported for VSD 3.4 and VSD 3.3.

After a discussion we decided to drop the idea to save the status of the check boxes even for only the box "encrypt for others".

Using gpg4win-5.0.0-beta369 @ win10 I can't reproduce it with use-keyboxd, but without use-keyboxd:

In T6117#205379, @ikloecker wrote:

I guess this is a typo because the CSR looks like an encryption-only certificate.

I think this will make the dialog less user friendly because with this change one always needs to check the status of all check boxes. Without the change the check boxes always have the same status when the dialog is opened the same way. Predictability is very important for usability and even more for accessibility.

I would like to change this ticket to "Save status of all check boxes in the sign/encrypt dialog".

ok, changed the text in the description of the ticket accordingly, but put two more "team" back in.

Dialogtext (winzige Politur):

We decided to

We got new suggestions for this:

Upstream MR: https://codereview.qt-project.org/c/qt/qtbase/+/676173

I found and fixed a bug (likely a regression in the new code): When CN_prefill or EMAIL_prefill is configured as true and no fixed CN or EMAIL is configured then Kleopatra should prefill Name and Email with values taken from CONFIGDIR/emaildefaults (used by KDE apps on Linux), from the Windows user or from the EMAIL environment variable. This didn't work anymore.

To query the AD I used the GPGME function gpgme_op_assuan_transact_ext with an query string like this:

ad_query --subst --attr=dn,userAccountControl (&(objectcategory=person)(objectclass=user) (|(userPrincipalName={{email}}) (mail={{email}})))

Of course {{email}} must be replaced with the mail address queried, this might probably also be the UserPrincipalName.