- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 15 2021
So, please show us gpg-error-config-test.log by your build.
Dec 14 2021
Ok, I have subscribed to the mailing list. I have resent the DCO.
DCO has not appeared on mailing-list. You can this from check list archives, https://lists.gnupg.org/pipermail/gcrypt-devel/2021-December/thread.html
Thanks Jussi, I did not receive the list moderator's email so I am not sure if the it has been posted on gcrypt-devel@gnupg.org. If not, I can resend the DCO. Thanks.
I did some finishing touches on coding style:
On import. Please use gnupg-devel mailing list for further API questions. This is a bug tracker and not a help forum.
Dec 13 2021
Hi Jussi,
Thank you for the answer then! You can probably review our guide then https://github.com/ossf/great-mfa-project/blob/main/guide/token-usage-guide.md :)
A clumsy workaround for the Kleo bug is to put "keyserver ldap:///" into the global gpg.conf after an ignore section containing keyserver. This will let gpgconf emit "ldap:///" unless a local gpg.conf exists.
Nice. The way with KS_GET and assuan is much better then I thought about using a temporary home and a --locate-key
Thanks. If I'm reading correctly, that fix was pushed in July. Any idea when the next release might come out?
Thank you for your report.
Dec 12 2021
Few comments on new patch:
Thanks for the offer. However, the core developers are using tokens for more than a decade meanwhile. We even make our own tokens ;-).
Dec 11 2021
Dec 10 2021
Hi jukivili,
The first is a warning and the other error codes are exactly what we want.
Adding comments, fixing "const" qualifier, I pushed the change.
Thank you, applied.