Not sure, what to expect, but generally looks fine for me in gpg4win-5.0.0-beta336 @ win10:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mon, Jun 30
In T7610#202487, @timegrid wrote:
- compliance note in sign/encrypt next to sign/encrypt button (both for file and clipboard) unreadable in black/nr1/nr2 and also in dark mode:
I guess, that's ok then, moving this to done.
Thanks, confirmed then, moving to Done.
In T7594#202471, @timegrid wrote:Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).
Issue with pretty kyber names moved into: T7708.
Moving this to done.
General issues with unformatted fingerprints/keyids moved into T7707.
In T7232#202509, @timegrid wrote:With above configuration it seems to work on gpg4win-5.0.0-beta336 @ win10.
Any way to verify in kleopatra, that the setting was applied?
In T7394#202514, @timegrid wrote:
- Kyber algorithms display only their ecc part
I guess that the missing formatting of fingerprint or key ID isn't restricted to v5 keys. -> separate ticket
In T7345#202503, @timegrid wrote:
- Some/Most "Not VS-NfD compliant" notes do not have the (beta) suffix (probably fine?)
Ingo tested this and it worked.
Looks good to me on gpg4win-5.0.0-beta336 @ win10:
- Full stops are fine now
- "not VS-NfD compliant" for invalid signatures not shown anymore (tested in vsd compliance mode)
Looks good to me on gpg4win-5.0.0-beta336 @ win10:
With above configuration it seems to work on gpg4win-5.0.0-beta336 @ win10.
Any way to verify in kleopatra, that the setting was applied?
Tested on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
I tested the VSD elements on gpg4win-5.0.0-beta336 @ win10 (beta compliance mode).
Happens also in the group config (warning icon):
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Fri, Jun 27
Mostly looks good to me on gpg4win-5.0.0-beta336 @ win10/win11.
Related? In smartcards view:
Thu, Jun 26
Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).
This also happens on Linux. And even with the Fusion style.
Thanks for the Windows 11 screen shots.
We decided to only add a green check mark (or red X in case it fails) on the left side in the message frame.
Thanks for the feedback. The issues are the same as on win10:
After discussion with Ingo and others it seems that separate Kleo processes per GNUPGHOME would confuse more users than being helpful for power users. Considering the use case of gpgpass the conclusion was to add an option to Kleo which allows to start is as a certificate manager without doing the UniqueApplicaiton thing and also entirely quit after closing the window.
Regarding the "unsure" findings:
- invalid state in cert list tooltip (red on black)
Wed, Jun 25
- Issues found
What about including the output of
On gpg4win-5.0.0-beta330 everything works fine again (both smime and openpgp regardless of expiration).
Tue, Jun 24
I now imported all certs in testzertifikate_2023/ (smime and openpgp) and generated a new one (openpgp, default settings, expiration 2028) and still get no valid signing certs in okular
added gpgsm log:
Ingo mentioned some maybe related expiration year 2038+ ticket, but I only found one for kleo: https://dev.gnupg.org/T7069
Issue about no valid smime certs found on signing split into: https://dev.gnupg.org/T7697
This is more a technical ticket. There's not really something to test. Setting to Resolved/Done as discussed with ebo.
Note that the first screenshot shows still "Sign/Encrypt" as button text instead of "Finish", but I didn't notice that again after this
Most issues with icons in high contrast modes (of Windows 10) should have been fixed. Needs to be verified especially with the high contrast modes of Windows 11.
Setting to Testing.
Moving to QA. All changes should be in the latest beta.
Many issues have been fixed. Setting to Testing to check what I have missed.