I looked the gpg-agent.log, it indeed suggested the problem fixed in rG61aea64b3c17: scd: Fix the use case of verify_chv2 by CHECKPIN., which is included in 2.2.24.

Nov 19 2020, 11:54 AM · gnupg (gpg22), Bug Report

• werner committed rDb386778c678e: web: More links to git repos. (authored by • werner).

web: More links to git repos.

Nov 19 2020, 10:02 AM

TaaviE created T5148: gnupg.org mail server doesn't encrypt outgoing mail.

Nov 19 2020, 9:47 AM · dev.gnupg.org

TaaviE added a comment to T5143: YubiKey 5 Nano GPG --card-edit verify command causes a segfault.

Building and installing 2.2.24 at least made it not crash, the very least it's an improvement in that respect.

Nov 19 2020, 9:36 AM · gnupg (gpg22), Bug Report

• werner committed rDee81abe357a2: web: Add a link to the Libgcrypt repo. (authored by • werner).

web: Add a link to the Libgcrypt repo.

Nov 19 2020, 9:29 AM

• gniibe claimed T5143: YubiKey 5 Nano GPG --card-edit verify command causes a segfault.

You have multiple readers and using PC/SC by specifying reader-port.
We fixed in master by T4998: scdaemon: PC/SC "No such device" without reader-port, and I didn't know similar fixes should be backported.
I will soon.

Nov 19 2020, 9:24 AM · gnupg (gpg22), Bug Report

• werner committed rG6594dc31f589: gpgconf: Also print revision of libksba. (authored by • werner).

gpgconf: Also print revision of libksba.

Nov 19 2020, 9:14 AM

• werner committed rG4070f302e4de: gpgconf: Also print revision of libksba. (authored by • werner).

gpgconf: Also print revision of libksba.

Nov 19 2020, 9:11 AM

• werner triaged T5143: YubiKey 5 Nano GPG --card-edit verify command causes a segfault as High priority.

Nov 19 2020, 8:41 AM · gnupg (gpg22), Bug Report

• werner committed rGf7cbf68fdd1e: po: Update Polish translation (authored by Jakub Bogusz <qboosh@pld-linux.org>).

po: Update Polish translation

Nov 19 2020, 8:35 AM

mgorny reopened T5039: 2.2.22 regression: Nitrokey Pro 2 is no longer recognized automatically, requires --card-status as "Open".

The problem seems to have returned in 2.2.24.

Nov 19 2020, 8:29 AM · Restricted Project, gnupg (gpg22), Bug Report

• werner added a comment to rG84020385be19: scd:openpgp: Public keys should be available for check_keyidstr..

Urgs, that was my fault.

Nov 19 2020, 8:16 AM

• gniibe committed rG8ddadbbdbbe2: agent: Fix creating shadow key on card key generation. (authored by • gniibe).

agent: Fix creating shadow key on card key generation.

Nov 19 2020, 7:52 AM

• gniibe reopened T5065: scdaemon doesn't detect card removal after boot/resume (Identiv SPR332v2) as "Testing".

Nov 19 2020, 5:58 AM · Restricted Project, gnupg (gpg22), scd, Bug Report

• gniibe added a comment to T5065: scdaemon doesn't detect card removal after boot/resume (Identiv SPR332v2).

Thanks again for your report.

Nov 19 2020, 5:57 AM · Restricted Project, gnupg (gpg22), scd, Bug Report

• gniibe committed rG84020385be19: scd:openpgp: Public keys should be available for check_keyidstr. (authored by • gniibe).

scd:openpgp: Public keys should be available for check_keyidstr.

Nov 19 2020, 5:56 AM

• gniibe committed rGe45455d3020c: gpg: Fix --card-edit command. (authored by • gniibe).

gpg: Fix --card-edit command.

Nov 19 2020, 5:13 AM

turkja added a comment to T5065: scdaemon doesn't detect card removal after boot/resume (Identiv SPR332v2).

I'm still having problems with 2.2.24. Now the card removal is detected correctly, but the initialization fails.

Nov 19 2020, 3:48 AM · Restricted Project, gnupg (gpg22), scd, Bug Report

• gniibe added a comment to T5137: gpg-agent 2.x poor performance / futex errors.

Thanks. I understand the situation. Basically, gpg-agent's computation is done by a single thread (in current implementation), although it accepts many requests simultaneously.

Nov 19 2020, 3:21 AM · Feature Request, gpgagent

Nov 18 2020

• werner added a comment to T5143: YubiKey 5 Nano GPG --card-edit verify command causes a segfault.

We had some card related regressions in 2.2.23. I would appreciate if you could first test again with 2.2.24 which was released yesterday.

Nov 18 2020, 6:19 PM · gnupg (gpg22), Bug Report

• werner closed T5147: I cannot decrypt as Invalid.

I am sorry, but this is not a help desk but a bug tracker. See https://gpg4win.org or https://gnupg.org to find out which community support is available.

Nov 18 2020, 6:15 PM · Support

Stockton created T5147: I cannot decrypt.

Nov 18 2020, 5:30 PM · Support

• werner committed rD378a3ba87a36: swdb: Release of libksba 1.5.0 (authored by • werner).

swdb: Release of libksba 1.5.0

Nov 18 2020, 5:05 PM

• werner committed rK9c0a818cd89c: Release 1.5.0 (authored by • werner).

Release 1.5.0

Nov 18 2020, 4:59 PM

• werner committed rKb301c95868e5: Post release updates (authored by • werner).

Post release updates

Nov 18 2020, 4:59 PM

• werner committed rKb426d2216583: Add SPDX identifiers. (authored by • werner).

Add SPDX identifiers.

Nov 18 2020, 4:59 PM

• ikloecker lowered the priority of T5130: Kleopatra: Generating OpenPGP keys on Yubikey (with PIV enabled) fails with "General error" from High to Normal.

Resetting priority to normal for re-evaluation

Nov 18 2020, 4:31 PM · kleopatra, Bug Report

• ikloecker reopened T5130: Kleopatra: Generating OpenPGP keys on Yubikey (with PIV enabled) fails with "General error" as "Open".

Re-opening. Now trying to generate new keys fails with a "Wrong card" error.

Nov 18 2020, 4:29 PM · kleopatra, Bug Report

• werner created T5146: Release Libksba 1.5.0.

Nov 18 2020, 4:11 PM · Release Info, libksba

• werner committed rKb6438e768cf9: Allow for NDEF list of certs and CRLs in CMS. (authored by • werner).

Allow for NDEF list of certs and CRLs in CMS.

Nov 18 2020, 4:01 PM

• aheinecke committed rM88294023c196: cpp: Use portable off_t size_t (authored by • aheinecke).

cpp: Use portable off_t size_t

Nov 18 2020, 3:18 PM

• ikloecker committed rKLEOPATRAccd6e3eecf7d: Merge branch 'gpgme-1.13.1' into 'master' (authored by • ikloecker).

Merge branch 'gpgme-1.13.1' into 'master'

Nov 18 2020, 2:55 PM

• ikloecker committed rKLEOPATRA9e475a6f3573: Bump required GPGME version to 1.13.1 (authored by • ikloecker).

Bump required GPGME version to 1.13.1

Nov 18 2020, 2:50 PM

• ikloecker committed rKLEOPATRA0c42b4a78ef9: Merge branch 'gpgme-1.13.1' into 'master' (authored by • ikloecker).

Merge branch 'gpgme-1.13.1' into 'master'

Nov 18 2020, 2:45 PM

• aheinecke committed rKLEOPATRA57248775932d: Improve error handling of seckey export (authored by • aheinecke).

Improve error handling of seckey export

Nov 18 2020, 2:40 PM

• aheinecke committed rKLEOPATRA4ccbaec62569: Respect action restrictions in welcomewidget (authored by • aheinecke).

Respect action restrictions in welcomewidget

Nov 18 2020, 2:40 PM

• aheinecke committed rKLEOPATRAf573a51f86fa: Pass UTF-8 filenames to gpgtar on Windows (authored by • aheinecke).

Pass UTF-8 filenames to gpgtar on Windows

Nov 18 2020, 2:40 PM

• aheinecke committed rKLEOPATRA30306bea3efe: Bump version in master (authored by • aheinecke).

Bump version in master

Nov 18 2020, 2:40 PM

• ikloecker committed rLIBKLEO79f68d55776f: Merge branch 'gpgme-1.13.1' into 'master' (authored by • ikloecker).

Merge branch 'gpgme-1.13.1' into 'master'

Nov 18 2020, 2:37 PM

• ikloecker committed rLIBKLEO92c3f01a2a1d: Bump required GPGME version to 1.13.1 (authored by • ikloecker).

Bump required GPGME version to 1.13.1

Nov 18 2020, 2:35 PM

andrey.arapov added a comment to T5137: gpg-agent 2.x poor performance / futex errors.

In T5137#139066, @werner wrote:

Note that you actually run 30 independent processes with gpg 1.4 but with gpg-agent there is just one process to handle the private key operations (decrypt). To utilize more cores you need to setup several GNUPGHOME with the same private keys.

Nov 18 2020, 2:33 PM · Feature Request, gpgagent

andrey.arapov added a comment to T5137: gpg-agent 2.x poor performance / futex errors.

In T5137#139064, @gniibe wrote:

I think that it is not gpg-agent but pinentry which causes millions of futex syscall errors.
For interactive use case, pinentry may be the point of contention.
I might be wrong if your key is not protected by passphrase.

If possible, please try adding arguments for gpg invocation: --pinentry-mode loopback --passphrase-file YOUR_FILE_FOR_PASSPHRASE
This can avoid the invocation of pinentry entirely.

Nov 18 2020, 2:32 PM · Feature Request, gpgagent

• ikloecker committed rKLEOPATRA5e5d740f91ea: Merge branch 'gpgme-1.13.1' into 'master' (authored by • ikloecker).

Merge branch 'gpgme-1.13.1' into 'master'

Nov 18 2020, 2:14 PM

• ikloecker added a comment to T5141: GnuPG: Make quick-gen-key work for keys on PIV cards.

Output of (unpatched) gpg with --debug ipc:

$ GNUPGHOME=$HOME/.cache/gnupg-master-home gpg --debug ipc --quick-gen-key --yes piv@example.net card
gpg: reading options from '[cmdline]'
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: enabled debug flags: ipc
gpg: DBG: chan_3 <- OK Pleased to meet you, process 7588
gpg: DBG: connection to the gpg-agent established
gpg: DBG: chan_3 -> RESET
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION ttyname=/dev/pts/7
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION ttytype=xterm-256color
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION display=:0
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION xauthority=/home/ingo/.Xauthority
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION putenv=XMODIFIERS=@im=local
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION putenv=GTK_IM_MODULE=cedilla
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION putenv=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION putenv=QT_IM_MODULE=xim
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION lc-ctype=de_DE.UTF-8
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION lc-messages=de_DE.UTF-8
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.3.0-beta1481
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION allow-pinentry-notify
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> OPTION agent-awareness=2.1.0
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> SCD SERIALNO
gpg: DBG: chan_3 <- S SERIALNO FF020001008A7796
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> SCD SERIALNO
gpg: DBG: chan_3 <- S SERIALNO FF020001008A7796
gpg: DBG: chan_3 <- OK
gpg: Serial number of the card: FF020001008A7796
gpg: DBG: chan_3 -> SCD LEARN --keypairinfo
gpg: DBG: chan_3 <- S CHV-USAGE 40 00
gpg: DBG: chan_3 <- S CHV-STATUS -2 3 -2
gpg: DBG: chan_3 <- S KEYPAIRINFO EB6A99D61EF3BC7C7934173CD9833376D773E65D PIV.9A a
gpg: DBG: chan_3 <- S KEYPAIRINFO 482BD076054B6950A6FC476C356AF029A5115BBD PIV.9E a
gpg: DBG: chan_3 <- S KEYPAIRINFO 0773CFCB90C043F3A6151B3F2FBF23726F10A48A PIV.9C sc
gpg: DBG: chan_3 <- S KEYPAIRINFO ED6579C1360100BE92C46ECB1A1826A63614D5AB PIV.9D e
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> SCD GETATTR $SIGNKEYID
gpg: DBG: chan_3 <- S $SIGNKEYID PIV.9C
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> SCD READKEY --info -- PIV.9C
gpg: DBG: chan_3 <- S KEYPAIRINFO 0773CFCB90C043F3A6151B3F2FBF23726F10A48A PIV.9C sc - nistp256
gpg: DBG: chan_3 <- [ 44 20 28 31 30 3a 70 75 62 6c 69 63 2d 6b 65 79 ...(118 byte(s) skipped) ]
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> SCD SERIALNO
gpg: DBG: chan_3 <- S SERIALNO FF020001008A7796
gpg: DBG: chan_3 <- OK
gpg: Serial number of the card: FF020001008A7796
gpg: DBG: chan_3 -> SCD LEARN --keypairinfo
gpg: DBG: chan_3 <- S CHV-USAGE 40 00
gpg: DBG: chan_3 <- S CHV-STATUS -2 3 -2
gpg: DBG: chan_3 <- S KEYPAIRINFO EB6A99D61EF3BC7C7934173CD9833376D773E65D PIV.9A a
gpg: DBG: chan_3 <- S KEYPAIRINFO 482BD076054B6950A6FC476C356AF029A5115BBD PIV.9E a
gpg: DBG: chan_3 <- S KEYPAIRINFO 0773CFCB90C043F3A6151B3F2FBF23726F10A48A PIV.9C sc
gpg: DBG: chan_3 <- S KEYPAIRINFO ED6579C1360100BE92C46ECB1A1826A63614D5AB PIV.9D e
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> SCD GETATTR $ENCRKEYID
gpg: DBG: chan_3 <- S $ENCRKEYID PIV.9D
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> SCD READKEY --info -- PIV.9D
gpg: DBG: chan_3 <- S KEYPAIRINFO ED6579C1360100BE92C46ECB1A1826A63614D5AB PIV.9D e - rsa2048
gpg: DBG: chan_3 <- [ 44 20 28 31 30 3a 70 75 62 6c 69 63 2d 6b 65 79 ...(286 byte(s) skipped) ]
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> RESET
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> READKEY -- 0773CFCB90C043F3A6151B3F2FBF23726F10A48A
gpg: DBG: chan_3 <- ERR 67141713 No such file or directory <GPG Agent>
Key generation failed: No such file or directory
gpg: secmem usage: 0/32768 bytes in 0 blocks

Nov 18 2020, 2:12 PM · gnupg (gpg23)

• aheinecke created T5145: gpgsm: Export secret key failures return zero.

Nov 18 2020, 1:58 PM · S/MIME, gnupg

• ikloecker closed T5142: Qt gpgme's sign_key function should not set a remark with an empty string as Resolved.

Fixed. Workaround for gpgme 1.15 (and earlier) implemented in Kleopatra: Do not call setRemark() with an empty QString.

Nov 18 2020, 1:55 PM · gpgme, qt, Bug Report

• ikloecker committed rKLEOPATRAbba1d9547252: Do not set an empty remark to avoid an empty signature notation (authored by • ikloecker).

Do not set an empty remark to avoid an empty signature notation

Nov 18 2020, 12:51 PM

• ikloecker committed rM3c185c2159cd: qt: Avoid empty "rem@gnupg.org" signature notations (authored by • ikloecker).

qt: Avoid empty "rem@gnupg.org" signature notations

Nov 18 2020, 12:48 PM

• ikloecker added a comment to T5142: Qt gpgme's sign_key function should not set a remark with an empty string.

I think Kleopatra is affected. It calls setRemark() on the job unconditionally with the text from the widget, and I'm pretty sure that this text is empty but not a null QString, if the user doesn't enter a remark.

Nov 18 2020, 12:24 PM · gpgme, qt, Bug Report

• aheinecke committed rO04aedef30681: Only restore orig body when it is not empty (authored by • aheinecke).

Only restore orig body when it is not empty

Nov 18 2020, 12:22 PM

• ikloecker created T5144: scd: Fails/crashes on SCD LEARN --keypairinfo for NetKey cards.

Nov 18 2020, 12:07 PM · Restricted Project, gnupg (gpg23), scd

TaaviE created T5143: YubiKey 5 Nano GPG --card-edit verify command causes a segfault.

Nov 18 2020, 11:17 AM · gnupg (gpg22), Bug Report

• werner added a comment to T5098: Gpg4win problems for Windows Users with some non-ASCII account names.

It was a bunch or work and we are still not able to pass Unicode strings on the command line. Will eventually be done. At least people in Asia can now use their regular Windows account with gpg.

Nov 18 2020, 10:41 AM · gnupg (gpg22), Windows

• werner added a comment to T5141: GnuPG: Make quick-gen-key work for keys on PIV cards.

Yes sure. --debug ipc should give you some insight why gpg does not thing the key is on the card.

Nov 18 2020, 10:39 AM · gnupg (gpg23)

• werner assigned T5142: Qt gpgme's sign_key function should not set a remark with an empty string to • ikloecker.

Ingo, can you please check? I guess we are not affected because Kleo already checks for an empty string. But dkg's suggestion sounds good to me.

Nov 18 2020, 10:34 AM · gpgme, qt, Bug Report

dkg created T5142: Qt gpgme's sign_key function should not set a remark with an empty string.

Nov 18 2020, 9:38 AM · gpgme, qt, Bug Report

• ikloecker placed T5141: GnuPG: Make quick-gen-key work for keys on PIV cards up for grabs.

Nov 18 2020, 9:37 AM · gnupg (gpg23)

bernhard added a comment to T5098: Gpg4win problems for Windows Users with some non-ASCII account names.