@timegrid I would not tag this ticket with LDAP, as it is not LDAP specific
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Thu, Dec 18
State in Gpg4win-5.0.0-beta446 and vsd 3.3.4 is this:
So the message is "Update Failed" for keyserver and "not found" for WKD.
In light of that the ticket is this old, I'll leave it at that instead of discussing further improvements beyond this single phrase.
These would have to go in a new ticket.
Wed, Dec 17
This is really weird behavior. It seems other secret keys in the keyring may also change to "undefined" validity when the certification is done with another key. And something about the key which is certified is important.
But it can also happen that it is enough to just import a secret key without certifying anything with it for it to be shown as "undefined" validity.
This task is obsolete as we do no longer use the Temp directory for encryption (I believe since vsd3.3.0/gpg4win 4.4.0). Instead the file is written directly to the target location with the ending ".part". It is renamed there after the encryption is completed.
The aim of this ticket is to map the message in Kleo for the corresponding gpg case to the "Not found" error in gpgsm and thus show the other message instead.
Tue, Dec 16
ok, yes, looks like this was not thought through. How about "Sign/Encrypt settings"?
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.
Mon, Dec 15
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.
Fri, Dec 12
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.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…
Tue, Dec 9
Fri, Dec 5
Thu, Dec 4
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.
Wed, Dec 3
Fri, Nov 28
I would say this is done.
Thu, Nov 27
Additionally to the issue Andre cited years ago, we also did some changes to fix other how signed/encrypted mails are shown, which are also relevant for the inbox. This 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)
Wed, Nov 26
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.
