I applied the keyboxd part for SETEPHEMERAL command, as it doesn't break anything.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Thu, Mar 26
Wed, Mar 25
Here is an attempt to fix the client side:
Tue, Mar 24
Pushed the change: rG533bcc265e9c: common:dotlock: Clean up for error/info/warning message.
While I pushed the change of libgcrypt, I'd like to apply following change to GnuPG.
This is more kind than GPG_ERR_BAD_PASSPHRASE by gcry_pk_testkey failure.
Mon, Mar 23
I retract my patch in T8171#215603
@m.eik gave us this link: https://github.com/ProtonMail/go-crypto/issues/184
It had already fixed in: rG55b5928099ba: dirmngr: Change the default keyserver.
And then in: rGa2f2523b99ff: Remove the default keyserver.
With same reason for T3852, I close this ticket.
GPGME has been divided into new GpgME, QGpgme, GpgMEpp, and GpgME-python.
And new QGpgme uses CMake now.
Fri, Mar 20
Pushed the change of gpgme: rM8b89678aed6d: Fix passphrase cancel handling.
Pushed the last change: rG2239f687bb14: scd:openpgp: UI improvement for use of PIN-entry.
Thu, Mar 19
It seems that pinentry-curses defaults to "OK".
(my branch for GTK-4, same.)
This is a bit larger change (of UI improvement):
Wed, Mar 18
I sent a patch to gcrypt-devel mailing list for the preparation of the change of RSA secret key checking.
If enabled, wrong RSA secret key (wrong means: under the Libre/OpenPGP specification) is rejected at import when gpg-agent calls gcry_pk_test_key.
I consider again about Ben's change. It could be simply support of the detection of the cancel situation where gpgme should return GPG_ERR_CANCELED (not related to single cancellation vs. whole cancellation).
Tue, Mar 17
I investigated the introduction of STATUS_CANCELED_BY_USER and GPGME_STATUS_CANCELED_BY_USER:
rG31e47dfad0f4: gpg: Add canceled status message.
rM35ca460019ea: Parse STATUS_CANCELED_BY_USER.
For OpenSSH, ssh-agent spec. defines p, q, and qInv.
FIPS has: FIPS 186-5 and SP 800-56Br2.