Looks good to me on gpg4win-5.0.0-beta357 @ win10:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mon, Aug 4
The advantage of using a fingerprint for referencing a key is that there won't be any collisions in the keyid. Further this unifies the schema with an LDS (Windows) installation where DNs must anyway be unique. But take care the client needs to support this new flag. This will be the case for gnupg >= 2.5.12 (cf. T7756)
Do you have a gpgme log?
I created a new issue for the "Keine Daten" error: T7768
Looks good to me on gpg4win-5.0.0-beta357 @ win10
Looks good to me on gpg4win-5.0.0-beta357 @ win10:
1.11.2 has been release see T7642
Release done.
Applied the change above.
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:
Sun, Aug 3
Sat, Aug 2
Fri, Aug 1
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.