User Details
- User Since
- Dec 7 2021, 3:55 PM (208 w, 3 d)
- Roles
- Administrator
- Availability
- Busy Busy until Nov 4 2030.
Yesterday
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.
Tue, Nov 25
For our Okular, we should not use the standard file names (okularrc, …) as this would conflict with a regular Okular installation.
Mon, Nov 24
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.
The preference option does already exist, it is "Prefer S/MIME". If not set (the default), then OpenPGP keys are preferred.
Thu, Nov 20
The tool tip for the menu is missing.
Please add the typical "Save at" dialog (instead of automatic saving with info "Key was saved at"). We should have consistent behavior when saving secret (and public) keys.
Tue, Nov 18
Mon, Nov 17
works with Gpg4win-5.0.0-beta395, too
Fri, Nov 14
@werner sees no reason to define a new status error for everything in gpg. So let's stick with this Kleopatra ticket and adding the "Audit Log"/"Diagnostics" button.
Yes, we now plan to add an "Show Audit Log" Button (or is it "Diagnostics" in this case?). But we are not sure if this is enough.
Thu, Nov 13
it is probably not worth the effort to backport this
Note: We would need to handle possibly diverse error cases. A network share could be configured e.g. to not allow deletion for the user so that the temporary file can not be deleted.
