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.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Dec 3 2024
Dec 3 2024
• 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.
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
• 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 [...]
• 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
• 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
• 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'
Dec 2 2024
Dec 2 2024
• werner triaged T7373: gpg --export-secret-keys exits with General error if the password prompt was canceled as Normal priority.
This ticket is obsolete
This doesn't look like a problem in Kleopatra.
• 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.
• gniibe closed T7426: Retain binary representation of key for import->export (in particular, Ed25519 signature) as Resolved.
OK, it's done. closed.
Nov 30 2024
Nov 30 2024
I get this message even with --quiet:
Nov 29 2024
Nov 29 2024
Fixed in 2.5.0 and 2.4.6.
Fixed in 2.4.6.
Fixed in 2.4.6.
Nov 28 2024
Nov 28 2024
• werner set External Link to https://lists.gnupg.org/pipermail/gnupg-announce/2024q4/000487.html on T7353: Release GnuPG 2.4.7.
Nov 26 2024
Nov 26 2024
dkg updated the task description for T7106: Trailing newline trouble in clearsigned message generation and verification.
Nov 25 2024
Nov 25 2024
• 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.
Nov 22 2024
Nov 22 2024
• 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.
• 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.
• werner triaged T7425: gpg --assert-pubkey-algo claims that ed25519 is stronger that ed448 as Low priority.
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:
Nov 14 2024
Nov 14 2024
• ikloecker changed the status of T7397: Kleopatra: Support Kyber generation, a subtask of T6636: PQC Implementation, from Open to Testing.
Nov 6 2024
Nov 6 2024
• ikloecker raised the priority of T7373: gpg --export-secret-keys exits with General error if the password prompt was canceled from Low to Needs Triage.
Nov 5 2024
Nov 5 2024
• ikloecker triaged T7373: gpg --export-secret-keys exits with General error if the password prompt was canceled as Low priority.
This looks as if it is resolved. Should I be wrong, you can reopen it.
Nov 4 2024
Nov 4 2024
• ebo changed the status of T7322: Kleopatra: General error if ADSK is not configured correctly from Open to Testing.
Nov 3 2024
Nov 3 2024
Oct 31 2024
Oct 31 2024
• ikloecker moved T7322: Kleopatra: General error if ADSK is not configured correctly from Backlog to WiP on the vsd33 board.
Werner backported this to GnuPG 2.2.45.
• ebo moved T7322: Kleopatra: General error if ADSK is not configured correctly from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo added a project to T7322: Kleopatra: General error if ADSK is not configured correctly: Restricted Project.
ok, regarding better access to the more detailed error dialog see the above mentioned ticket
Oct 30 2024
Oct 30 2024
Sorry, I've pasted the wrong link, I wanted to paste this one: https://lists.gnupg.org/mailman/listinfo/gnupg-users
Why would I turn to the Windows mailing list when I am a Linux user?
I removed a duplicated comment above.
Please do not duplicate information (no top posting) and keep your descriptions short and to the point.
"BTW, GnuPG 2.3.4 is a very old version."
wiktor-k added a comment to T4060: Add ability to mark critical notations as "recognized" during signature verification.
I've checked and can confirm this is working as intended.
In the story of my life, you are a mythological figure.
• ikloecker reassigned T7313: gpgconf --list-options does not handle multiple trusted-keys. from • ikloecker to • werner.
Kleopatra just checks if the option "default-new-key-adsk" is set (i.e. it doesn't matter if it's an option with scalar value or list value). The other two options that were changed are not used by Kleopatra.
• werner triaged T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key as Normal priority.
• werner renamed T7354: Leak of User-ID via clipboard from Major Security Issue: Leak of User-ID via clipboard to Leak of User-ID via clipboard.
• werner added a comment to T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.
I reviewed this and there are actually two changes. The first chnage
is a simple string change from
Oct 29 2024
Oct 29 2024
ametzler1 added a comment to T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.
Hello,
I have a hard time to agree that is the right thing for gnupg to throw an error if it successfully imported a revocation certificate for an expired key. This is a meaningful (and not useless) change even if the key is expired.
Tested again on linux with current master (at 18081e2ecf43de2be6ad5a7ca3384e1e2b66914d) and 2.2 (at 5c0383d558cc9112c4c0984a3b2a6c98b29a92ca) - still same behavior.
• werner edited projects for T6500: Keyserver access via http-proxy isn't attempted when using standard-resolver, added: gnupg; removed gnupg24.
• werner edited projects for T6679: Keyboxd: SQL database disk image is malformed, added: gnupg, Support; removed gnupg24.
In T7322#192972, @ebo wrote:Which is of course technically correct but why can't we have the much more clear "invalid ADSK ... specified"? I think this would help troubleshooting.
Was fixed in master with rG374195e741cf1c52daad6c07799d308c8a9f73e3 (bug tag was missing in the commit).
• werner moved T4060: Add ability to mark critical notations as "recognized" during signature verification from Backlog to QA for next release on the gpgme board.
Alright, finally supported by gpgme (fot 1.24) For testing you may use
• ebo edited projects for T7322: Kleopatra: General error if ADSK is not configured correctly, added: vsd33; removed vsd33 (vsd-3.3.0).
• ebo added a project to T7322: Kleopatra: General error if ADSK is not configured correctly: vsd33 (vsd-3.3.0).
This is not on any workboard. But I tested it with 4win-Beta-64 and the error shown in Kleopatra is now "Unusable public key".
So I'll put it on vsd33.
Oct 28 2024
Oct 28 2024
• werner added a comment to T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.
Indeed, gpg fixes a long standing bug in that expired trusted-keys were not correctly handled. Thus this error message
Oct 27 2024
Oct 27 2024
Oct 25 2024
Oct 25 2024
• werner edited projects for T4060: Add ability to mark critical notations as "recognized" during signature verification, added: gnupg; removed gnupg (gpg22).
Solved for gnupg 2.2, 2.4 and 2.6. GPGME support still missing.
Oct 23 2024
Oct 23 2024
• werner closed T6185: `gpg2 --list-keys --with-colons > /dev/full` exits with status 0 as Resolved.
Also done for gpgsm in gnupg26 (master)
Oct 22 2024
Oct 22 2024
Oct 16 2024
Oct 16 2024
• ikloecker added a project to T7332: Kleopatra: Initial keylisting sometimes fails or hangs for some seconds: gnupg.
The fix should probably be backported to gnupg 2.2 and 2.4.
Oct 15 2024
Oct 15 2024
I'm still seeing the same problems both with current master and 2.2
FWIW, the cache has not been implemented in 2.4 (which will be used for the next gpg4win) and thus there is no need for a fix there.
Was fixed last Thursday with commit rG69a8aefa5bf77136b77383b94e34ba784c1cce89 for 2.2 and will soon make it to master.
Oct 14 2024
Oct 14 2024
Oct 11 2024
Oct 11 2024
Oct 8 2024
Oct 8 2024
gpg4win 4 has been released with unicode support. Closing.
• gniibe changed the status of T7316: Curve25519/v5 key cannot be exported, a subtask of T7315: Allow exporting of PQC keys., from Open to Testing.
Pushed the fix for exporting OpenPGP v5 key: rG57dce1ee62c2: common,gpg,scd,sm: Fix for Curve25519 OID supporting new and old.
Oct 7 2024
Oct 7 2024
• ikloecker triaged T7322: Kleopatra: General error if ADSK is not configured correctly as Normal priority.
With the new patch you get this now:
[GNUPG:] KEY_CONSIDERED F40ADB902B24264AA42E50BF92EDB04BFF325CF3 1 [GNUPG:] ERROR add_adsk 53 gpg: key "F40ADB902B24264AA42E50BF92EDB04BFF325CF3!" not found: Unusable public key gpg: Did you specify the fingerprint of a subkey? [GNUPG:] FAILURE gpg-exit 33554433
Oct 4 2024
Oct 4 2024
• ikloecker added a project to T7322: Kleopatra: General error if ADSK is not configured correctly: gnupg.
Yes, gpg logs "invalid ADSK ... specified", but it doesn't emit a status error. This needs to be changed in gpg.
Test on a dedicated Windows box (T 460, i5-6300U@2.40GHz, harddisk):
| VSD Version | gpg version | Load time |
| 3.1.26 | 2.2.41 | 1:59 |
| 3.2.4 beta-2 | 2.2.45 beta 25 | 0:46 |
Overall effect of these changes tested on a small Windows VM is only 47 -> 26 seconds. Did also tests with --kbx-buffer-size but that does not make it better than the default, either.
Oct 3 2024
Oct 3 2024
The OID is used for fingerprint computation, which complicates things.
Oct 2 2024
Oct 2 2024
• werner lowered the priority of T7313: gpgconf --list-options does not handle multiple trusted-keys. from Normal to Low.
Using the shorter OID for v5 is on purpose; thus we need to fix the export.
Oct 1 2024
Oct 1 2024
Sep 30 2024
Sep 30 2024
Will be available in 2.2.45 and 2.5.2
Now we are at 4 seconds. Available in master and 2.2.
Sep 27 2024
Sep 27 2024
With that patch we are down to about 6 seconds.
Sep 26 2024
Sep 26 2024
Sep 25 2024
Sep 25 2024
• werner edited projects for T5085: Filter APDUs in log output, added: gnupg; removed gnupg24, gnupg22.
• werner edited projects for T5446: Don't show LDAP credentials in error messages, at least not by default, added: gnupg, dirmngr; removed gnupg22.
• werner edited projects for T6820: SCD: Invalid ID when decrypting with brainpool key , added: gnupg, Not A Bug; removed Restricted Project, gnupg22.
• gniibe closed T6641: pinentry-tty & pinentry-curses breaks tty when timeout occurs or CTRL-C is pressed as Resolved.
Fixed in pinentry 1.3, when using GnuPG 2.4 or later.
Sep 24 2024
Sep 24 2024
Possible fix:
From 24e8191ab5de7245cf6063be778b6d3ceec4414b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ingo=20Kl=C3=B6cker?= <dev@ingo-kloecker.de> Date: Tue, 24 Sep 2024 10:44:31 +0200 Subject: [PATCH] gpg: Fix --quick-set-expire for V5 subkey fingerprints
Sep 17 2024
Sep 17 2024
For now, I'm using this to avoid failure of make check (invoking gpg-agent by gpg-connect-agent).
diff --git a/common/stringhelp.c b/common/stringhelp.c index 9a2265258..6596c65cd 100644 --- a/common/stringhelp.c +++ b/common/stringhelp.c @@ -70,6 +70,22 @@ change_slashes (char *name) { #ifdef HAVE_DOSISH_SYSTEM char *p; + /* 0: don't know yet, 1: it's under wine, -1: no */ + static int semihosted_by_wine; + + /* Under wine, no change. */ + if (!semihosted_by_wine) + { + HMODULE hntdll = GetModuleHandle ("ntdll.dll"); + if (hntdll + && GetProcAddress (hntdll, "wine_get_version")) + semihosted_by_wine = 1; + else + semihosted_by_wine = -1; + } + + if (semihosted_by_wine > 0) + return name;
Sep 12 2024
Sep 12 2024
See new subtask T7290 for smartcards and the link entries mentioned above.