- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 11 2022
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.
Oct 10 2022
Works here with gpg 2.3.8-beta58 on Linux. Maybe gpg 2.2 does not properly report the cancelled pinentry.
Oct 9 2022
In T5790#163980, @manonfgoo wrote:
Oct 8 2022
In T5790#163886, @werner wrote:[Merging didn't work]
Can you test the Patch, does it work for you ?
Thanks. Fix has been pushed to master.
Oct 7 2022
One more nit regarding to the test is the format string for size_t which was using %d instead of %zu. This is fixed by the attached patch:
Here is the patch as file:
The patch applies with -p1 to the master brach, alternatively I could push a commit, but my user does not seam to be allowed to do so:
[Merging didn't work]