- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Dec 4 2024
Dec 4 2024
Add a configure test for gettid.
swdb: gpgme 1.24.1
• werner closed T7397: Kleopatra: Support Kyber generation, a subtask of T6636: PQC Implementation, as Resolved.
Works for me in an NSIS installer. The VSD beta thing also works with copied conf files.
(gpg4win-5.0.0-beta27 with some local mods)
• TobiasFella committed rKLEOPATRA96a0ac995fc3: Fix crash when output directory for decryption doesn't exist (authored by • TobiasFella).
Fix crash when output directory for decryption doesn't exist
• ikloecker closed T5944: Kleopatra: Recipient input is confused about secondary user IDs as Resolved.
This doesn't happen anymore now that we offer all valid user IDs and not just the primary user IDs.
• aheinecke added a comment to T5982: GpgOL: More fine grained discovery of content-id / embedded parts .
Maybe its overthinking the problem of attachments with content-id but no reference in the HTML (btw. if mails are shown as plain text all attachments are listed regardless of their content id. ) I guess code like: if filename.endsWith(.png) || filename.endsWith(.jpg) || filename.endsWith(.jpeg) then ignore_cid=false; else ignore_cid = true. Would do the right thing 99% of the time. Core reference: rOd87848059727587be1f660283e0aeb3be16cc382
• 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.
• 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.
• werner committed rG7b0be541a994: w32: Introduce Registry key GNUPG_ASSUME_COMPLIANCE. (authored by • werner).
w32: Introduce Registry key GNUPG_ASSUME_COMPLIANCE.
Require gpgrt 1.51
• werner committed rWc1ee440e535b: Fix uninstalling of gpg-disable-keyboxd.bat (authored by • werner).
Fix uninstalling of gpg-disable-keyboxd.bat
• 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.
l10n daemon script <scripty@kde.org> committed rKLEOPATRA0d30b7146be9: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
l10n daemon script <scripty@kde.org> committed rKLEOPATRAa8b811aa9bc5: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
l10n daemon script <scripty@kde.org> committed rKLEOPATRA4df17e049532: GIT_SILENT made messages (after extraction) (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT made messages (after extraction)
Dec 3 2024
Dec 3 2024
• ikloecker added a comment to T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog.
Looks like there's something not correct in the completion model. Or we use different criteria for showing the blue "i" (as "information") which doesn't make it better. Reopen?
• 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.
• 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
• ikloecker moved T6663: Kleopatra: change option "publish on keyserver" from Backlog to WIP on the gpd5x board.
• ikloecker changed the status of T6663: Kleopatra: change option "publish on keyserver" from Open to Testing.
This is long done, but only for Qt 6-based releases. Andre's comment T6663#175481 has also been addressed.
• 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.
• werner renamed T7436: Allow ssh to sign data larger than the assuan line length. from Allow ssh to sign larger data than the assuan line length. to Allow ssh to sign data larger than the assuan line length..
• ikloecker moved T6627: Kleopatra: Add checkbox in certifications dialog from Backlog to WIP on the gpd5x board.
• ebo renamed T7436: Allow ssh to sign data larger than the assuan line length. from Allow ssh to sign larger data tha the assuan line length. to Allow ssh to sign larger data than the assuan line length..
• 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 changed the status of T6627: Kleopatra: Add checkbox in certifications dialog from Open to Testing.
This is long done, but only for Qt 6-based releases.
• ikloecker removed a project from T6553: Kleopatra: Expiry date issues and improvements: Restricted Project.
• ebo added a comment to T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog.
Tested Gpg4win 4.4:
Interesting, when you search for the UID, it looks as before, with the green check mark:
cleanup: Use else if directly
Remove richt text support
webserver: Only listen on localhost
• ikloecker moved T7435: Kleopatra: Show Details does not work for certificates selected as Encrypt for others from Backlog to WiP on the vsd33 board.
Backported for VSD 3.3 / Gpg4win 4.4.1.
Update NEWS
• ikloecker committed rKLEOPATRAa866bfed3b65: Fix showing Certificate Details for the user ID's certificate (authored by • ikloecker).
Fix showing Certificate Details for the user ID's certificate
• werner triaged T7436: Allow ssh to sign data larger than the assuan line length. as Normal priority.
• ikloecker changed the status of T7435: Kleopatra: Show Details does not work for certificates selected as Encrypt for others from Open to Testing.
I'll backport this for VSD 3.3 / Gpg4win 4.4.1. Regression risk is minimal.
• ikloecker committed rKLEOPATRA282f224cfd3d: Fix showing Certificate Details for the user ID's certificate (authored by • ikloecker).
Fix showing Certificate Details for the user ID's certificate
• ikloecker changed the status of T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog from Open to Testing.
I think this is resolved. In the Sign/Encrypt dialog we now offer the individual user IDs instead of the certificates, i.e. the two user IDs of the Udo certificate are both offered and one should be listed as certified and the other one as not certified (if one is certified and the other one isn't; for me both user IDs are ultimately trusted).
• TobiasFella committed rKLEOPATRAb1aec91a760f: Don't fail when canceling one file (authored by • TobiasFella).
Don't fail when canceling one file
• TobiasFella committed rKLEOPATRA2137db97d5a0: Also handle errors this way (authored by • TobiasFella).
Also handle errors this way
• TobiasFella committed rKLEOPATRAc3a1a8aa3e66: Process files that cannot be read the like most other errors (authored by • TobiasFella).
Process files that cannot be read the like most other errors
• 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.
• 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'
Minor cleanness fix for autogen.sh
• ebo added a project to T7405: Kleopatra: Highlight if no valid encryption subkey exists: Feature Request.
Closing this as duplicate of T7405. That ticket has the better task description as it was made after discussing offline how it could best be done.
• ebo removed a project from T5950: Allow viewing expired certificates more easily: Restricted Project.
closing this as duplicate for the improvement part, the support part is solved, anyway.
T6109 is also closely related and I think it would be addressed by this ticket.
Update NEWS
• ikloecker moved T5780: Kleopatra: Result dialog does not have focus after operation from Backlog to WiP on the vsd33 board.
Backported for VSD 3.3.x / Gpg4win 4.4.1
• ikloecker committed rKLEOPATRA6b6016328392: Ensure that decryption result dialog is visible (authored by • ikloecker).
Ensure that decryption result dialog is visible
• ikloecker added a project to T5780: Kleopatra: Result dialog does not have focus after operation: vsd33.
I'll backport this because this issue is a really bad usability problem for people using the Windows Explorer integration to decrypt files. And the regression risk is minimal.
• ikloecker changed the status of T5780: Kleopatra: Result dialog does not have focus after operation from Open to Testing.
For me the change fixes the problem on Windows. (I haven't checked if there was a problem on Linux/X11, but I have verified that the change also works on Linux/X11.)
• ikloecker committed rKLEOPATRAcbe21024c974: Ensure that decryption result dialog is visible (authored by • ikloecker).
Ensure that decryption result dialog is visible
Typo fixes for the NEWS.
• ebo moved T7413: Kleopatra: Smartcard action buttons in case of p15 cards are sometimes not responsive from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo edited projects for T7413: Kleopatra: Smartcard action buttons in case of p15 cards are sometimes not responsive, added: vsd33, Restricted Project; removed gpd5x.
I think you are right, it is fixed. I tried it now again with Gpg4win 4.4 with several cards and it works as you describe.
l10n daemon script <scripty@kde.org> committed rKLEOPATRA25982067a58b: GIT_SILENT made messages (after extraction) (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT made messages (after extraction)
l10n daemon script <scripty@kde.org> committed rKLEOPATRAf3897283fce0: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
Joshua Goins <josh@redstrate.com> committed rMTP228f6fa77ae7: Remove explicit quit connection with QQmlApplicationEngine (authored by Joshua Goins <josh@redstrate.com>).
Remove explicit quit connection with QQmlApplicationEngine
Joshua Goins <josh@redstrate.com> committed rMTP7bd6d29ef63e: Remove explicit quit connection with QQmlApplicationEngine (authored by Joshua Goins <josh@redstrate.com>).
Remove explicit quit connection with QQmlApplicationEngine
heirecka committed rKLEOPATRA0475ad743030: GIT_SILENT Update Appstream for new release (authored by heirecka).
GIT_SILENT Update Appstream for new release
heirecka committed rKLEOPATRAd6f23290bb0a: GIT_SILENT Upgrade release service version to 24.12.0. (authored by heirecka).
GIT_SILENT Upgrade release service version to 24.12.0.
heirecka committed rKLEOPATRAee1c62adbfed: GIT_SILENT Update Appstream for new release (authored by heirecka).
GIT_SILENT Update Appstream for new release
Dec 2 2024
Dec 2 2024
CarlSchwan committed rKLEOPATRA88b3c4ee8630: Add screenshots for AppStream (authored by CarlSchwan).
Add screenshots for AppStream
This also happens if one activates the Kleopatra main window, then activates the Windows Explorer and then starts a decrypt&verify operation.
I have seen this when doing the following:
- Start Kleopatra and minimize its window
- Start decrypt&verify operation for an encrypted archive in Windows Explorer with GpgEX
• ikloecker closed T5839: GNUPGEX Explorer File Encryption Tar Archive long Filename Bug as Resolved.
Gpg4win 4.4.0 has just been released. Creation of encrypted archives has been completely reworked with Gpg4win 4.3.0 already. I could create an encrypted archive containing the two files with GpgEX without problems.
Christoph refers to this post here:
https://forum.gnupg.org/t/readme-4-3-1-en-txt-currently-missing-from-files-gpg4win-org/5845/4
• ikloecker removed a project from T5824: Kleopatra: Full accessibility support: Restricted Project.
• ikloecker added a comment to T7413: Kleopatra: Smartcard action buttons in case of p15 cards are sometimes not responsive.
I tried to reproduce this with Gpg4win 4.4.0, but it worked for all PKCS#15 cards I tried (dark blue R&S, Genua, ipt.fraunhofer). As soon as the certificates were imported from the card (and a "Do you trust this root certificate" dialog was canceled) the buttons became enabled.
Gpg4win 4.4.0 has just been released. I cannot reproduce unexpected results when doing a lookup on server. Unfortunately, many keyservers do not publish the user IDs (i.e. name and/or email address) anymore. Kleopatra does not list results without user IDs because GnuPG won't import them anyway.
This has been fixed in the meantime. If you should still experience this problem with Gpg4win 4.4.0 then reopen this ticket.
• ebo moved T6984: Kleopatra: Add icon for folder encryption from QA to vsd-3.3.0 on the vsd33 board.
CarlSchwan committed rKLEOPATRAc88153f08cdf: Add screenshots for AppStream (authored by CarlSchwan).
Add screenshots for AppStream
• werner triaged T7373: gpg --export-secret-keys exits with General error if the password prompt was canceled as Normal priority.
Gpg4win 4.4.0 has just been released. I assume that this has been fixed in the meantime. In particular, "General error" should happen a lot less. If the problem still occurs with Gpg4win 4.4.0 then reopen the ticket.
• werner committed rE7baf9f6b4030: po: Update Portuguese Translation. (authored by Daniel Cerqueira <dan.git@lispclub.com>).
po: Update Portuguese Translation.
• werner committed rG7b0d49785d0e: po: Update Portuguese Translation. (authored by Daniel Cerqueira <dan.git@lispclub.com>).
po: Update Portuguese Translation.