ok, yes, looks like this was not thought through. How about "Sign/Encrypt settings"?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 16 2025
This relates to T7917: Check for revocation of the ADSK's original subkey
The expected behavior is that only "Ted" (the key from where the ADSK originates) is listed, regardless of ADSKs, on every listing.
Because for regular keys there can only ever be one, "gpg -k" shows always only one key.
Subkeys which are ADSKs shall therefore never be listed with this command.
Tested with Gpg4win-5.0.0-beta446, identically to the procedure from the description:
ok, then this ticket will be for improvement of the usability.
Dec 15 2025
This is still the case in Gpg4win-5.0.0-beta413
It is not entirely clear what was meant here.
Probably it is about a command line option for opening the group config from Outlook/GpgOL or KMail. Which would be useful.
Dec 12 2025
This was resolved some at time in the past
@svuorela Isn't this done already for KF6?
@werner : is this already testable?
isn't this done?
Tested VSD 3.3.4: Fingerprints can be copied in the certificate list with select and CTRL+C. CRTL+V then will insert the fingerprint without spcaes
setting this to resolved, werner already tested this
we haven't seen this in a while…
Dec 9 2025
Dec 5 2025
Dec 4 2025
I believe the reason was simply that we wanted it short, "Upload successful." sounds better than"Publication successful." and I associate keyserver more with upload than publication. Furthermore "Certificate successfully published" has the disadvantage of being correct only for the upload of one certificates, not multiple. So you'd have to have case differentiation.
Dec 3 2025
Nov 28 2025
I would say this is done.
Nov 27 2025
Additionally to the fix Andre cited years ago, we also did some more changes recently in regard to how signed/encrypted mails are shown. Which are relevant for the inbox, too.
This issue should be fixed.
This is a duplicate of T7833: GpgOL: Security level 2 shown for manually imported and certified cert
Ok, then this is only an issue in the VSD versions. (I confirmed with a quick test with Gpg4win-5.0.0-beta413)
Nov 26 2025
It would be possible as a workaround in Kleopatra to show any identical entries only once. Saving after that will not add any more entries.
Nov 25 2025
For our GnuPG Okular, we should not use the standard file names (okularrc, …) as this would conflict with a regular Okular installation.
Nov 24 2025
I wonder if we should better open a new ticket with all the relevant data when we get a report giving more information and set this one to invalid.
And meanwhile I have tested this a bit with VSD3.3.3 and in the case that the sender has a valid and *VS-compliant* key the automatic switching works.
Possibly include a preference for whether OpenPGP or S/MIME is checked first.
Nov 20 2025
The tool tip for the menu is missing.
And after the "Save at" dialog we here get a "Secrete Team key was saved to $PATH/$filename" notification window. The one for secret key backup has no location info and for public keys we have no message at all.
We should have consistent behavior when saving secret (and public) keys, imho.