User Details
- User Since
- Jul 24 2020, 9:57 AM (266 w, 1 d)
- Availability
- Busy Busy until Jul 29 2030.
Yesterday
Thu, Aug 28
Mon, Aug 25
I don't see the problem. The pattern "Kyber768" is ambiguous because it matches the user IDs of both keys. The match is a simple substring match. There's no logic for "exact match" and no heuristic for "better match". If you want to ensure that a specific key is chosen then you must use a unique identifier for the key. Best use the fingerprint.
Thu, Aug 21
Backported for VSD 3.4
Backported for VSD 3.4
Backported for VSD 3.4
Backported for VSD 3.4
Backported for VSD 3.4
Backported for VSD 3.4
Backported for VSD 3.4
Backported for VSD 3.4
In the meantime pinentry has been updated also for VSD 3.4.
Backported for VSD 3.4
Backported for VSD 3.4
Wed, Aug 20
Mon, Aug 18
This task is not really actionable. Moreover, it proposes a technical solution instead of just stating the problem that needs to be solved. There may be better solutions, e.g. in the Notepad I decided to move the focus to the message widget that contains the result to make the screen reader read the result.
I've also fixed the problem that a file named mail.P7M was not treated as encrypted email message. I think this could be tested/verified.
After studying the logs created by NVDA and its source code I strongly suspect that the problem needs to be fixed in NVDA. NVDA tries to avoid repeating the text of common ancestors of the old and the new focus object, but it fails to detect the Create OpenPGP Certificate dialog as common ancestor of the text edit field in this dialog and the Error (child) window.
Wed, Aug 13
Fixed by adding a patch for Qt 6 (and a patch for Qt 5 in gpg4win-4-branch for VSD 3.4).
Mon, Aug 11
Logging all
Fri, Aug 8
Thu, Aug 7
Fixed and backported for VSD 3.4
Wed, Aug 6
Solved by focusing the result message after the notepad operation is complete. I think that's an acceptable compromise for ensuring that users of assistive tools are informed about the result even if the focus is moved to a different UI element (which, in general, should be avoided because users can get lost).