If a certificate is in more than one group, this will not work...
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 14 2022
It seems to me there are two separate concerns here:
I have now backported the missing error reporting to gnupg 2.2 (rG6f0066db2c87: gpg: Report an error for receiving key from agent.). Please retest once gpg 2.2.41 is included in GnuPG (VS-) Desktop 3.x.
Pushed the change, although it is not enabled yet (since the feature will be only available by newer libgcrypt, 1.11).
Pushed.
Pushed to master.
By 1/N...5/N, it works. And it shows the API needs clarification and possible modification/fixes; As written in the comment of system-w32.c, fd == POSIX fd semantics is good, which asks API/ABI break.
Thank you, confirmed. Pushing the fix.
Oct 13 2022
$ ping git.gnupg.org
PING git.gnupg.org (217.69.76.56) 56(84) bytes of data.
64 bytes from cvs.gnupg.org (217.69.76.56): icmp_seq=1 ttl=58 time=6.74 ms
64 bytes from cvs.gnupg.org (217.69.76.56): icmp_seq=2 ttl=58 time=6.87 ms
You need to assign a drive letter.
Oct 12 2022
Thanks. It seems gnupg 2.2 is missing rG605ab99912ac: gpg: Report an error for receiving key from agent.. I'll backport this commit.
Oct 11 2022
is there any news for gnupgp 4.0.4 release with gnupg 2.3.8?
My suggestion is to clearly state that there is a direct Key Signature with an expiration date. Another feature would be to add a separate command to modify Direct Key Signatures. However, the latter has the problem that it help with proliferation of such signatures and other OpenPGP implementation will run into other problems. Thus for the whole ecosystem such an option is might not be a good idea.
Hidden where?
Thanks for looking into this!
Direct key signatures are rarely used. IIRC, we implemented that the same way PGP did it.
Fixed in libgpg-error 1.46 and pinentry 1.2.1.
Fixed in 1.6.1.
Fixed in 1.6.1.