- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 25 2024
ok. For the tooltip I would now favor the same addition to all current tool tips where it applies:
"(w/o disabled ones)", e.g. "All certificates (except disabled ones)".
Oh. I should have noticed that. Thanks for fixing.
Fixed in pinentry 1.3, when using GnuPG 2.4 or later.
Sep 24 2024
Fixed. The fix is in gpg4win so that it will automatically apply for VSD 3.3.
works, gpg4win-beta-50
This is a regression of a fix for T6073: Kleopatra: Fix issues with high contrast resp. inverted color scheme.
Please go ahead and apply to master. I'll take then care of backporting.
icon is there, gpg4win-Beta-50
I would exclude them.
For comparison: That's how it looks like with the Breeze style on Linux. The highlighting background on Windows is way too light.
works, gpg4win-Beta-50. "Write" occurs at the right point now.
search for "example" works now, Gpg4win-Beta-50
What about all other filters? For example "Not Certified", "Not Fully Certified", "My Own", "OpenPGP"? Should the disabled certificates also be excluded for those filters?
Possible fix:
From 24e8191ab5de7245cf6063be778b6d3ceec4414b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ingo=20Kl=C3=B6cker?= <dev@ingo-kloecker.de> Date: Tue, 24 Sep 2024 10:44:31 +0200 Subject: [PATCH] gpg: Fix --quick-set-expire for V5 subkey fingerprints
Okay, okay: s/private key/secret key/
ok, discussed this with Werner and Alexander, result was:
Fixed in libassuan 3.0.0.
Done in GnuPG 2.5.0.
Sep 23 2024
I'd write: "This means that the data you want to decrypt was not encrypted to any of your private keys."
Sep 21 2024
Sep 20 2024
The test with Gpg4win 4.3.1 (using GnuPG 2.4) seems to indicate that:
- gpg didn't update the trustdb automatically after importing the extended trusted certificate.
- gpg updated the trustdb automatically after deleting and re-importing the expired trusted certificate, but Kleopatra still showed the certificates signed by the trusted certificate as "certified". This could be a bug in the trustdb calculation (note the log message "Schlüssel C5D6C919005F36A4 ist als ultimativ vertrauenswürdig gekennzeichnet" which could indicate that gpg treats the key as valid although it's expired). On the other hand, my test with GnuPG 2.4 on Linux doesn't reproduce this problem.
