gnupgProject
ActivePublic
Watch Project

Milestones
View All

gpg14
Milestone

Subprojects
View All

common
Project
g10
Project
gnupg22
Project
gnupg24
Project

Members

This project does not have any members.
View All

Watchers (2)

Details

Description

Bugs, feature requests, memos, and support related to GnuPG.

Note that the tags gnug24, gnupg26 etc are used to indicate that a certain task is scheduled to be fixed in that version. This tag here is used if there is no concrete version affected or a schedule has not yet been set.

Recent Activity
View All

Yesterday

• gniibe closed T7192: gnupg-2.5.0: Use gpgrt_process_spawn API (was: Does not build due to undeclared identifier 'environ') as Resolved.

Fri, Dec 6, 1:05 AM · gnupg, Bug Report

Thu, Dec 5

• werner closed T7193: gnupg-2.5.0: Does not build due to missing declaration of read and write as Resolved.

Thu, Dec 5, 4:36 PM · MacOS, gnupg, Bug Report

• werner closed T7316: Curve25519/v5 key cannot be exported, a subtask of T7315: Allow exporting of PQC keys., as Resolved.

Thu, Dec 5, 4:32 PM · gnupg26, OpenPGP, PQC, gnupg

• werner closed T7316: Curve25519/v5 key cannot be exported as Resolved.

Thu, Dec 5, 4:32 PM · gnupg26, OpenPGP, PQC, gnupg

• werner closed T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key as Resolved.

Thu, Dec 5, 4:30 PM · gnupg, Bug Report

• werner added a comment to T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.

@ilf: Yes these message are emitted using log_info in 2.4.7 and 2.5.2. Thus they don't case a failure exit. I will silence them with --quiet in 2.5.3.

Thu, Dec 5, 4:28 PM · gnupg, Bug Report

• werner moved T7289: Release GnuPG 2.5.2 from Backlog to Done on the gnupg26 board.

Thu, Dec 5, 11:48 AM · gnupg, Release Info, gnupg26

• werner updated the task description for T7289: Release GnuPG 2.5.2.

Thu, Dec 5, 11:47 AM · gnupg, Release Info, gnupg26

• werner triaged T7442: Release GnuPG 2.5.3 as Normal priority.

Thu, Dec 5, 11:45 AM · Release Info, gnupg

Wed, Dec 4

• werner closed T7397: Kleopatra: Support Kyber generation, a subtask of T6636: PQC Implementation, as Resolved.

Wed, Dec 4, 2:46 PM · PQC, gnupg, libgcrypt

• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

I have created two subtasks for the two changes we could make in Kleopatra to avoid the gpg-agent startup race.

Wed, Dec 4, 11:29 AM · gnupg, kleopatra

• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

Neither gpg nor gpgsm start gpg-agent if the keyring is empty. That's why Andre made Kleo start gpg-agent explicitly so that people could get going with an empty keyring after inserting their (PKCS#15) smartcard.

Wed, Dec 4, 11:11 AM · gnupg, kleopatra

• werner added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

Kleo needs this only because it wants to directly talk to gpg-agent via Assuan. For example to get smartcard infos. What about delaying this part until you have received some data back from gpg or gpgsm? This makes sure that the agent has been started.

Wed, Dec 4, 10:07 AM · gnupg, kleopatra

Tue, Dec 3

• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

Yes, that's what happens. I did an experiment with waiting for gpgconf --launch gpg-agent to succeed, but the timeout of 5 seconds I used was too low and I didn't feel like increasing the timeout. Instead now we run gpgconf --launch gpg-agent detached.

Tue, Dec 3, 4:48 PM · gnupg, kleopatra

• werner added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

Let me guess: Kleopatra starts the agent using gpgconf --launch gpg-agent which in turn uses gpg-connect-agent to actually start the agent if needed. Kleopatra does not seem to wait for the launch to succeed and fires up gpg and gpgsm. They both wait for the gpg-agent to be started and both use the same locking strategy. However, this involves a pseudo random wait which should avoid deadlocks. See gnupg/common/dotlock.c:next_wait_interval

Tue, Dec 3, 4:34 PM · gnupg, kleopatra

• ikloecker changed the status of T6663: Kleopatra: change option "publish on keyserver", a subtask of T6626: Kleopatra: Improve certification and revocation, from Open to Testing.

Tue, Dec 3, 4:20 PM · kleopatra

• ikloecker changed the status of T6627: Kleopatra: Add checkbox in certifications dialog, a subtask of T6626: Kleopatra: Improve certification and revocation, from Open to Testing.

Tue, Dec 3, 4:14 PM · kleopatra

• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

I'm wondering what happened (or why nothing happened) between the exit of gpg-agent[2816] at 10:11:12 and the start of gpg-agent[6492] at 10:12:00.

Tue, Dec 3, 2:40 PM · gnupg, kleopatra

• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

scdaemon logged this:

2024-12-03 10:12:02 scdaemon[6272] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.scdaemon' gehÃ¶rt
2024-12-03 10:12:02 scdaemon[6272] Handhabungsroutine für fd -1 gestartet
2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> OK GNU Privacy Guard's Smartcard server ready, process 6272
2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 <- GETINFO socket_name
2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> D C:\Users\g10code\AppData\Local\gnupg\S.scdaemon
2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> OK
2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 <- OPTION event-signal=28c
2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> OK
2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 <- KEYINFO --list
2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> OK
[...]

Tue, Dec 3, 2:29 PM · gnupg, kleopatra

• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

gpgsm logged this:

2024-12-03 10:11:08 gpgsm[3940] enabled debug flags: ipc
2024-12-03 10:11:08 gpgsm[3940] enabled compatibility flags:
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> # Home: C:\Users\g10code\AppData\Roaming\gnupg
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> # Config: C:/Users/g10code/AppData/Roaming/gnupg/gpgsm.conf
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> # DirmngrInfo: C:\Users\g10code\AppData\Local\gnupg\S.dirmngr
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK GNU Privacy Guard's S/M server 2.4.7 ready, process 3940
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION ttyname=/dev/tty
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION enable-audit-log=1
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION allow-pinentry-notify
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION list-mode=1
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION with-validation=1
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION with-secret=1
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION offline=1
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK
2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- LISTKEYS 
2024-12-03 10:11:10 gpgsm[3940] Kein aktiver gpg-agent - `C:\\Program Files (x86)\\GnuPG\\bin\\gpg-agent.exe' wird gestartet
2024-12-03 10:11:10 gpgsm[3940] DBG: chan_0x000001a0 -> S PROGRESS starting_agent ? 0 0
2024-12-03 10:11:11 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:13 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:15 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:16 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:19 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:20 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:22 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:24 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:26 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:27 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:30 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:31 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:33 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:35 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:37 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:38 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:41 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:42 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:44 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:45 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:48 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:49 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:52 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:53 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:55 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:57 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:59 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:12:00 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK Pleased to meet you, process 6492
2024-12-03 10:12:03 gpgsm[3940] DBG: connection to the gpg-agent established
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> RESET
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> OPTION ttyname=/dev/tty
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> OPTION putenv=QT_QPA_PLATFORM=windows:darkmode=2
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> GETINFO version
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- D 2.4.7
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> OPTION allow-pinentry-notify
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> HAVEKEY 46B01CFBE21A10B2CFF41ABBD1D6A03E3F364121
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- ERR 67108881 Kein geheimer Schlüssel <GPG Agent>
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> ISTRUSTED 22FF41AB501FD708D10B0931E6F72A5C64DCF10E
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- S TRUSTLISTFLAG relax
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> KEYINFO 46B01CFBE21A10B2CFF41ABBD1D6A03E3F364121
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- ERR 67108891 Nicht gefunden <GPG Agent>
[...]
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x000001a0 <- BYE
2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x000001a0 -> OK closing connection
2024-12-03 10:12:03 gpgsm[3940] secmem usage: 0/16384 bytes in 0 blocks

Tue, Dec 3, 2:28 PM · gnupg, kleopatra

• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

gpg logged this:

2024-12-03 10:11:08 gpg[3936] enabled debug flags: ipc
2024-12-03 10:11:08 gpg[3936] enabled compatibility flags:
2024-12-03 10:11:08 gpg[3936] verwende Vertrauensmodell pgp
2024-12-03 10:11:10 gpg[3936] Kein aktiver gpg-agent - `C:\\Program Files (x86)\\GnuPG\\bin\\gpg-agent.exe' wird gestartet
2024-12-03 10:11:11 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:13 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:15 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:16 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:19 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:20 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:22 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:23 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:26 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:27 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:30 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:31 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:33 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:34 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:37 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:38 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:41 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:42 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:44 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:45 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:48 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:49 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:52 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:53 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:55 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock...
2024-12-03 10:11:58 gpg[3936] Warte bis der gpg-agent bereit ist ... (8s)
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK Pleased to meet you, process 6492
2024-12-03 10:12:02 gpg[3936] Verbindung zum gpg-agent aufgebaut
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> RESET
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> OPTION ttyname=/dev/tty
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> OPTION putenv=QT_QPA_PLATFORM=windows:darkmode=2
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> GETINFO version
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- D 2.4.7
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> OPTION allow-pinentry-notify
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> OPTION agent-awareness=2.1.0
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> HAVEKEY --list=1000
2024-12-03 10:12:02 gpg[3936] DBG: chan_0000027c <- [ 44 20 07 af f5 9c 99 cf cd 72 e0 c7 a6 af 8f 94 ...(942 byte(s) skipped) ]
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> KEYINFO 950A511AA08C9A16C9FA3DD1AA8C1E4BF43E0B0F
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- S KEYINFO 950A511AA08C9A16C9FA3DD1AA8C1E4BF43E0B0F D - - - P - - -
2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK
[...]
2024-12-03 10:12:03 gpg[3936] DBG: chan_0x0000027c -> KEYINFO 58C8BB90D9D8565156786B1F17C4C6E404237F3A
2024-12-03 10:12:03 gpg[3936] DBG: chan_0x0000027c <- S KEYINFO 58C8BB90D9D8565156786B1F17C4C6E404237F3A D - - - C - - -
2024-12-03 10:12:03 gpg[3936] DBG: chan_0x0000027c <- OK
2024-12-03 10:12:03 gpg[3936] secmem usage: 0/32768 bytes in 0 blocks

Tue, Dec 3, 2:26 PM · gnupg, kleopatra

• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

gpg-agent.log starts with

2024-12-03 10:11:12 gpg-agent[2816] Der Socket kann nicht an `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent' gebunden werden: Unknown error
2024-12-03 10:11:12 gpg-agent[2816] secmem usage: 0/32768 bytes in 0 blocks

Looks like gpg-agent tried to bind the socket and immediately exited when this failed. The logs of gpg-agent continue 48 seconds later with

2024-12-03 10:12:00 gpg-agent[6492] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent' gehÃ¶rt
2024-12-03 10:12:00 gpg-agent[6492] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.extra' gehÃ¶rt
2024-12-03 10:12:00 gpg-agent[6492] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.browser' gehÃ¶rt
2024-12-03 10:12:00 gpg-agent[6492] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.ssh' gehÃ¶rt
2024-12-03 10:12:00 gpg-agent[6492] gpg-agent (GnuPG) 2.4.7 started
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- RESET
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- OPTION ttyname=/dev/tty
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- OPTION putenv=QT_QPA_PLATFORM=windows:darkmode=2
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- GETINFO version
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> D 2.4.7
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- OPTION allow-pinentry-notify
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- OPTION agent-awareness=2.1.0
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- HAVEKEY --list=1000
2024-12-03 10:12:02 gpg-agent[6492] no running C:\\Program Files (x86)\\GnuPG\\bin\\scdaemon.exe daemon - starting it
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x000002a4 <- OK GNU Privacy Guard's Smartcard server ready, process 6272
2024-12-03 10:12:02 gpg-agent[6492] first connection to daemon C:\\Program Files (x86)\\GnuPG\\bin\\scdaemon.exe established
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x000002a4 -> GETINFO socket_name
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x000002a4 <- D C:\Users\g10code\AppData\Local\gnupg\S.scdaemon
2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x000002a4 <- OK
2024-12-03 10:12:02 gpg-agent[6492] DBG: additional connections at 'C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.scdaemon'

Tue, Dec 3, 2:24 PM · gnupg, kleopatra

• ikloecker created T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).

Tue, Dec 3, 2:21 PM · gnupg, kleopatra

Mon, Dec 2

• werner triaged T7373: gpg --export-secret-keys exits with General error if the password prompt was canceled as Normal priority.

Mon, Dec 2, 1:54 PM · Feature Request, gnupg26, gnupg

• ebo closed T4249: No connection to Keyserver possible as Resolved.

This ticket is obsolete

Mon, Dec 2, 1:36 PM · gnupg, dirmngr, Bug Report, gpg4win

• ikloecker removed a project from T4159: Kleopatra fails to create new Key Pair: kleopatra.

This doesn't look like a problem in Kleopatra.

Mon, Dec 2, 11:34 AM · gnupg, Bug Report, gpg4win

• ikloecker removed a project from T3601: GnuPG: Decryption on Windows Samba share is very slow: kleopatra.

Kleopatra now let's gpg deal with I/O directly. This makes decryption with Kleopatra as fast (or slow) as with gpg on the command line. Hence I'll remove the Kleopatra tag.

Mon, Dec 2, 9:50 AM · gpg4win, gnupg

• gniibe closed T7426: Retain binary representation of key for import->export (in particular, Ed25519 signature) as Resolved.

OK, it's done. closed.

Mon, Dec 2, 5:49 AM · gnupg

Sat, Nov 30

ilf added a comment to T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.

I get this message even with --quiet:

Sat, Nov 30, 12:15 PM · gnupg, Bug Report

Fri, Nov 29

• gniibe closed T7058: KDF-DO is not properly implemented as Resolved.

Fixed in 2.5.0 and 2.4.6.

Fri, Nov 29, 8:02 AM · scd, gnupg, Bug Report

• gniibe closed T7288: gpg is not properly handling IPGP entries as Resolved.

Fixed in 2.4.6.

Fri, Nov 29, 7:59 AM · dns, dirmngr, gnupg, Bug Report

• gniibe closed T7201: More memory leaks in gnupg as Resolved.

Fixed in 2.4.6.

Fri, Nov 29, 7:58 AM · gnupg, Bug Report

Thu, Nov 28

• werner set External Link to https://lists.gnupg.org/pipermail/gnupg-announce/2024q4/000487.html on T7353: Release GnuPG 2.4.7.

Thu, Nov 28, 1:03 PM · gnupg, Release Info

Tue, Nov 26

dkg updated the task description for T7106: Trailing newline trouble in clearsigned message generation and verification.

Tue, Nov 26, 11:24 PM · gnupg, Bug Report

Mon, Nov 25

• werner closed T7353: Release GnuPG 2.4.7 as Resolved.

Mon, Nov 25, 12:27 PM · gnupg, Release Info

• werner triaged T7428: Release GnuPG 2.4.8 as Low priority.

Mon, Nov 25, 12:11 PM · gnupg, Release Info

• werner changed the status of T7426: Retain binary representation of key for import->export (in particular, Ed25519 signature) from Open to Testing.

I cherry picked your patch for master and 2.4.

Mon, Nov 25, 11:13 AM · gnupg

Fri, Nov 22

• werner renamed T7425: gpg --assert-pubkey-algo claims that ed25519 is stronger that ed448 from gpg --assert-pubkey-algo cmails that ed25519 is stringer that ed448 to gpg --assert-pubkey-algo claims that ed25519 is stronger that ed448.

Fri, Nov 22, 4:58 PM · Bug Report, OpenPGP, gnupg

• werner closed T7425: gpg --assert-pubkey-algo claims that ed25519 is stronger that ed448 as Resolved.

For master fixed with rGbb6b38c24010258c7cb2da840d0a088fe43393b3 (Wrong bug id used).
Also fixed for gnupg24.

Fri, Nov 22, 4:58 PM · Bug Report, OpenPGP, gnupg

• werner triaged T7425: gpg --assert-pubkey-algo claims that ed25519 is stronger that ed448 as Low priority.

Fri, Nov 22, 4:42 PM · Bug Report, OpenPGP, gnupg

• ebo closed T7424: Kleopatra: Filter for QES suitable certificates does not work as Invalid.

It works, technically.
But for this to work you have to put the keyword "qual" at the end of the line of the system trustlist.txt file, the user trustlist.txt won't work. Example line:

Fri, Nov 22, 2:31 PM · gnupg, kleopatra