Applied the change above.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 4 2025
I realized that I enbugged in rG5efabec21883: gpg:ecc: Use the common function of gnupg_get_ecc_params..
It has been regression since 2.5.9.
Pushed the changes in {gniibe/synch-spawn} branch.
It consists of three commits:
Aug 3 2025
Aug 2 2025
Aug 1 2025
closing, rest in follow up ticket.
Turns out the cause is a wrong entry in the gpgsm.conf. Setting "dbug-level basic" without specifying an output file.
And encrypting a file is likewise affected.
Test on Windows by overwriting gpgtar from gpg4win-5.0.0-beta357 and also tested on Linux. Debian packages with patches are already available.
There is a new --keyserver-option update-before-send which is enabled by default.
the web client received some changes in the meantime and behaves more verbose regarding connections to a native client. we should check this again, especially if GpgOL/Web is supposed to be used for different outöook accounts at the same time.
in the meantime we decided it's not always desirable to have the process autostarted. therefore the current default (manual start) is considered ok, but if possible a configuration option should be implemented, so users can activate autostart if they find it useful.
Jul 31 2025
Kleopatra from VSD installations should now use gpgv from the GnuPG installed by VSD when verifying the signature of the VERSION file. GPD and Gpg4win installations both use gpgv from the GnuPG installed at the value of the registry key "Software\\GnuPG:Install Directory".
Closing this ticket, the task is done. Further improvements should go into a new tickets after we decided what we want.
Ok, setting this to done, but not resolved so that timegrid will notice it and make a new ticket with more information for the "no data" message.
In T7642#203189, @gniibe wrote:I wonder about GCC 15 preparation for the release. If it's good to have, three patches are needed to apply: