- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 9 2023
Sep 8 2023
This looks to me like the typical thing where you also do not get the "Diagnostics" button viewed. Because log-file is set in the various .conf files and the stderr does not get back to GPGME / Kleopatra so we have nothing to show there because the actual error ended up in a log file.
In T5960#175407, @ebo wrote:The result of your changes is a bit unexpected for me, maybe something is missing in the testversion Gpg4win-4.2.1-beta31?
[6064] org.kde.pim.libkleo: gpgConfGetConsoleOutputCodePage returns 65001 [6064] org.kde.pim.libkleo: stringFromGpgOutput trying to decode "" using codepage 65001
Was already with gpgme 1.21.0. Note that I used the done column but in future a milestone would be more useful than that catch all "done".
Also fixed for gnupg22
My issue was that it makes no sense to publish a revocation of a local certification...
I'm fine with it in the case if the certification was exportable.
Btw. if the keyserver is set to "none" or whatever the new value is worded we should remove all the publishing options from the UI. But that is a different issue, I just noticed this while talking about this ticket.
If I revoke a certificcation I am asked to "publish revocation".
When certifying there is the checkbox to publish.
Tested with current version. Works.
Sep 7 2023
this works now:
I think using a static const char * is better than using a macro. In fact, using a static constexpr std::string may be even better because we avoid calculating the string length during runtime again and again. (I'm not sure the compiler is clever enough to precalculate the string length of a static const char *.)
Tested at first with GnuPG-VS-Desktop-3.2.0.0-beta178 from 2023-08-29
@ebo: I just a did a test build: gnupg-vs-desktop-3.2.0-beta178-x86_64.AppImage in my directory
This has been well tested during development and is thus ready for a release.
Sep 6 2023
That should be easy on Unix but on Windows we have the nul nul: and iirc also /dev/nul.
ack
In T5960#175317, @ikloecker wrote:The previous two changes will hopefully fix the error output of export to server. I'm not entirely sure about the missing line breaks.
In T6556#175399, @werner wrote:@iklocker: Which gpg bug to you mean?
Then gettext_use_utf8 doesn't seem to be working as intended.
We have a fix for now and thus I lower the priority. Given that EasyPG mimics the GPGME API we should here also use another pipe to convey the passphrase (e.g. for symmetric encryption).
I don't see a value to do this for 2.2 and introduce a regression with that.
@iklocker: Which gpg bug to you mean?