Please see the 5-patch series posted on gnupg-devel for a fix for this.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Feb 6 2025
Feb 6 2025
dkg added a comment to T7511: `gpg --compliance=rfc4880 --quick-gen-key` produces a key that is not compatible with RFC 4880.
dkg added a comment to T7511: `gpg --compliance=rfc4880 --quick-gen-key` produces a key that is not compatible with RFC 4880.
Maybe we have a different understanding of what "backward compatibility" means. if someone needs backward compatibility to communicate with someone using an RFC 4880 client, then surely they don't want to use a pubkey algorithm that isn't specified in RFC 4880, right?
Feb 5 2025
Feb 5 2025
dkg added a comment to T7516: `gpg --compliance=rfc4880 --quick-add-key $fpr rsa sign` fails unnecessarily with "third-party key signatures using the SHA1 algorithm are rejected".
Patch sent to gnupg-devel. I think this can be applied to the 2.4 series as well.
• werner closed T7511: `gpg --compliance=rfc4880 --quick-gen-key` produces a key that is not compatible with RFC 4880 as Wontfix.
The compliance mode likes 4880 or 2440 are only here for backward compatibility in case that is needed. New keys shall always be generated using the current default algorithms. Note that a mode like de-vs is different in that it is used to comply with certain regulatory demands and not as a backward compatibility hack.
Feb 4 2025
Feb 4 2025
dkg added a comment to T7511: `gpg --compliance=rfc4880 --quick-gen-key` produces a key that is not compatible with RFC 4880.
i see two forms of an initial resolution here: one is to have set_compliance_option always explicitly set opt.def_newkey_algo. The other is to check opt.compliance in get_default_pubkey_algo.
Feb 3 2025
Feb 3 2025
I'm not sure what Kleopatra should do differently. Kleopatra relies on the error messages provided by gpgme which in turn relies on gpg's status messages.
• werner triaged T7488: Improve decryption error message caused by deleted card key as Normal priority.
Thanks. I applied all 4 patches to master and did one additional change to get --allow-old-cipher-algos straight.
Feb 2 2025
Feb 2 2025
Jan 31 2025
Jan 31 2025
Here's all of the above patches squashed into a single patch:
0001-gpg-The-last-compliance-option-supersedes-previous-o.patch5 KBDownload
.attached here is a series of 4 patches that reinforce that the last --compliance policy option (or equivalent option, like --rfc4880 or --gnupg) supercedes any earlier one.
sorry for the confusion in the initial report -- the policy compliance option is of course --compliance, and not --policy, and i just miswrote it in one line of the description above. I've corrected it now, and all the rest of the report is still as it was.
dkg updated the task description for T7501: policy compliance options collide incompatibly without warning.
That gpg seems to be some other or patched software than the one from gnupg:
Jan 27 2025
Jan 27 2025
This issue occurs when using GPGME with multiple contexts and setting the OpenPGP engines to different GnuPG home paths. As you mentioned, it is crucial to let gpgconf know the correct home path so that it can locate the socket file used by gpg-agent and properly clean up all instances.
• werner added projects to T7492: gpgconf failed to kill all gpgagent daemons on windows: gnupg, Windows.
gpgconf assumes that there is only one of the daemons. In fact it can only work with one and that is the one daemon which listens on the socket. all daemon's do a self-check by trying to connect to themself and terminate if they realize that they are not anymore the owner of the socket. As long as a daemon is started by a gnupg component a file system lock is taken to avoid duplicate launching. However it a daemon is stared by other means this could lead to a race.
Jan 24 2025
Jan 24 2025
• werner triaged T7487: libksba/gpgsm: support for RSA-PSS signatures made with a maximum saltLength value as Wishlist priority.
If you encounter real world certificates with these parameters we can bump up the priority.
Jan 23 2025
Jan 23 2025
• ebo renamed T7491: Kleopatra: Confusing additional pinentry on creation of new keypair with ADSK configured from Kleopatra: Confusing additional pinentry on while new keypair with ADSK configured to Kleopatra: Confusing additional pinentry on creation of new keypair with ADSK configured .
• werner triaged T7491: Kleopatra: Confusing additional pinentry on creation of new keypair with ADSK configured as Normal priority.
Jan 22 2025
Jan 22 2025
• ikloecker removed a project from T7491: Kleopatra: Confusing additional pinentry on creation of new keypair with ADSK configured : kleopatra.
Kleopatra has no influence on this. This does surely also happen when a new keypair is created on the command line.
Jan 20 2025
Jan 20 2025
Reported gnupg channel on IRC.
An ascii armored file in question was: https://github.com/syncthing/syncthing/releases/download/v1.29.2/sha256sum.txt.asc
When CHECKCRC == 0 (no CRC), ->any_data was not set, resulted
no valid OpenPGP data found.
wrongly.
Jan 19 2025
Jan 19 2025
zablockil added a comment to T7487: libksba/gpgsm: support for RSA-PSS signatures made with a maximum saltLength value.
I think I can understand you, too much complexity.
Jan 17 2025
Jan 17 2025
• werner added a comment to T7487: libksba/gpgsm: support for RSA-PSS signatures made with a maximum saltLength value.
See this comment which is related to T4538:
Jan 15 2025
Jan 15 2025
Werner says this won't be fixed…
Because the system can be configured to use constraints which we can't explain except in ABNF, which won't help users.
Jan 14 2025
Jan 14 2025
Note: The is a bug in the gnupg-w32-2.5.3 tarballs. After untaring cd to the directory as usual but then do:
rm PLAY/src/zlib/*.[oa] PLAY/src/bzip2/*.[oa]
before you run
make -f build-aux/speedo.mk this-native
• werner set External Link to https://lists.gnupg.org/pipermail/gnupg-announce/2025q1/000489.html on T7442: Release GnuPG 2.5.3.
• gniibe changed the status of T7478: _gpg_close_all_fds hangs on nwer Linux systems in a simple chroot w/o /proc/self/fd from Open to Testing.
• gniibe added a comment to T7478: _gpg_close_all_fds hangs on nwer Linux systems in a simple chroot w/o /proc/self/fd.
@werner I read the code of gpgme/src/posix-io.c. I understand the two points:
- For the correctness sake, the possible interrupted closefrom should be handled.
- we can share the code with closefrom case and non-closefrom case.
Jan 10 2025
Jan 10 2025
• gniibe closed T7457: gpg --full-gen-key doesn't show list of keys on card (regression) as Resolved.
Fixed in 2.5.3.
Jan 9 2025
Jan 9 2025
Jan 8 2025
Jan 8 2025
• werner added a comment to T7478: _gpg_close_all_fds hangs on nwer Linux systems in a simple chroot w/o /proc/self/fd.
@gniibe: Please see gpgme/src/posix-io.c where we have this:
• werner renamed T7478: _gpg_close_all_fds hangs on nwer Linux systems in a simple chroot w/o /proc/self/fd from `_gpg_close_all_fds` hangs on modern Linux when `/proc/self/fd` is unavailable; spawning a process without `GPGRT_SPAWN_INHERIT_FILE` takes > 1 hour to _gpg_close_all_fds hangs on nwer Linux systems in a simple chroot w/o /proc/self/fd.
• gniibe added a comment to T7478: _gpg_close_all_fds hangs on nwer Linux systems in a simple chroot w/o /proc/self/fd.
Thank you for your report.
Jan 7 2025
Jan 7 2025
All applied.
Dec 20 2024
Dec 20 2024
• ikloecker added a project to T7468: Kleopatra: General error when aborting subkey generation: gnupg.
Looks like gpg 2.2 doesn't emit a canceled status log message, but gpg 2.4 does if the problem only occurs with VSD but not with Gpg4win.
Dec 19 2024
Dec 19 2024
Installing language-pack-tr-base fixed the issue. Closing. Sorry for the noise.
Dec 18 2024
Dec 18 2024
In T7454#196228, @werner wrote:Actually not a bug: In my tests I forgot to unset LANGUAGES and LANG before calling gpg.
LANGUAGE= LANG= LC_MESSAGES=de_DE gpgThus this should work. But it did only work when I used
LANGUAGE= LANG= LC_MESSAGES=de_DE.UTF8 gpgThus the whole thing is related to the configuration of locale.alias and on whether LANGUAGE is set in the environment (for me it is set to en_US:en
Actually not a bug: In my tests I forgot to unset LANGUAGES and LANG before calling gpg.
Dec 16 2024
Dec 16 2024
• ebo moved T7322: Kleopatra: General error if ADSK is not configured correctly from WiP to QA on the vsd33 board.
• gniibe changed the status of T7457: gpg --full-gen-key doesn't show list of keys on card (regression) from Open to Testing.
It's a bug I introduced when fixing T7309.
Fixed in rGaa36f6ae8bae: gpg: Fix key generation with existing key from card.
Dec 13 2024
Dec 13 2024
• alexk placed T7457: gpg --full-gen-key doesn't show list of keys on card (regression) up for grabs.
Dec 12 2024
Dec 12 2024
• werner added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
Right, the first process is the gpg-connect-agent (via gpgconf). I used gpg just as an example. All processes use the same code to launch the agent.
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
There were three parties involved:
- gpgconf --launch gpg-agent
- gpg -k ...
- gpgsm --server followed by LISTKEYS command
• werner added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
Thinking again about this my hypothesis is:
• gniibe added a comment to T7368: dirmngr/dns.c files to compile due to type-mismatch caused by missing _XOPEN_SOURCE on Solaris and derivatives.
IIUC, simpler solution would be modifying m4/socklen.m4 adding Solaris variant specific code.
Tweaking _XOPEN_SOURCE requires the change of Autoconf (if done correctly), which would be larger surgery.
Dec 11 2024
Dec 11 2024
• werner added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
In T7434#195318, @ikloecker wrote: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.
• aheinecke added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
I am not sure if it helps if I comment, I just saw that this is issue cropped up again, and although we might be seeing different problems since other reports like T6623: Kleopatra hangs "Loading certificate cache" on Windows 10 T4581: Kleopatra stuck in loading the certificate cache are about indefinite hangs. (Was a timeout added in a generic place recently?) I just hope that at one point the underlying cause for this is found and resolved instead of hiding the symptom each time we find a way to reproduce this a bit better. Seeing T7437 and T7438 in which I commented a bit more made me sad that this is still not treated as a GnuPG issue.
Dec 6 2024
Dec 6 2024
Dec 5 2024
Dec 5 2024
• werner closed T7316: Curve25519/v5 key cannot be exported, a subtask of T7315: Allow exporting of PQC keys., as Resolved.
• werner closed T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key as Resolved.
• 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.
Dec 4 2024
Dec 4 2024
• werner closed T7397: Kleopatra: Support Kyber generation, a subtask of T6636: PQC Implementation, as Resolved.
• 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 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.
Dec 3 2024
Dec 3 2024
• 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 changed the status of T6663: Kleopatra: change option "publish on keyserver", 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, 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).
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'
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.