Strange. pinentry-tty has no place to report ENOENT. I wonder if you notified gpg-agent when you change the config (like gpgconf --reload gpg-agent).
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 4 2022
Feb 3 2022
The string 'Pinentry' is a module name, which is defined in libgpg-error.
It means, the error source is pinentry.
Feb 2 2022
Feb 1 2022
Pushed the change in rE433aba9e778e: build,tests: Fix detection of have_lock_optimization..
@marv Thank you for your report.
Jan 31 2022
Jan 28 2022
Jan 27 2022
@jukivili , thank you for your comment.
Jan 26 2022
Jan 25 2022
Thank you, applied both of two patches.
Thanks, fixed.
Jan 24 2022
struct thread_creation { void (*compute) (void *arg); void *arg; void (*create_done) (gcry_kdf_handle_t *hd, void *tid); };
Jan 20 2022
Test cases are recovered in rC535a4d345872: fips: Recover test cases for selftest, add skipping in FIPS mode..
Unfortunately, gdb session log and ktrace log don't have enough information to locate the cause/problem.
Jan 19 2022
Sorry, it's my misunderstanding.
_gcry_fips_run_selftest can be run by GCRYCTL_SELFTEST.
I was confused by the function name. Perhaps, it is good to change the name of function to _gcry_run_selftest.
@werner Those removed tests are selftests which are only invoked by FIPS mode for its requirement of selftests.
Pushed the change in rC76aad97dd312: fips: Reject shorter key for HMAC in FIPS mode..
Jan 18 2022
And we need to fix selftest for shorter keys.
@pmgdeb : IIUC, what we need is:
diff --git a/cipher/md.c b/cipher/md.c index 34336b5c..4f4fc9bf 100644 --- a/cipher/md.c +++ b/cipher/md.c @@ -903,6 +903,9 @@ prepare_macpads (gcry_md_hd_t a, const unsigned char *key, size_t keylen) { GcryDigestEntry *r;
Thank you, applied.
Jan 17 2022
Thank you, applied.
Also, add another change.
Backported to 2.2, too.
Jan 12 2022
Here is the backport to 2.2:
In the original code, register_trusted_keyid is used in keygen.c, so that it updates user_utk_list, thus, will be into utk_list.
This should be done, by adding the keyid to utk_list directly.
Things have been a bit buggy here (probably, since the beginning).
In g10/trustdb.c,
Let me clarify:
- It was on 2003-11-01 (ChangeLog is on 2003-10-31 probably in US): rG5c37fd90bf81: * trustdb.h, trustdb.c (register_trusted_keyid): New. Adds a keyid to the
Jan 11 2022
Thank you.
Applied.