S/MIME keys are not listed correctly
Open, HighPublic

Assigned To
Authored By
• TobiasFella
Oct 14 2024, 11:59 AM

Description

gnupg, gpgme, libkleo, kleopatra from master branch.

This shows as various problems in kleopatra, what I've noticed so far includes

  • Failure to decrypt/verify smime encrypted/signed files
  • All Root Certificates show up as untrusted even when they're trusted
  • own S/MIME key not shown in selection combo for selecting signing key
  • Some (not necessarily all) S/MIME keys missing from the list
  • Kleopatra crashing (due to being in a state that doesn't make sense)

Bisecting the gnupg repo points at ef2be95258d2e02659e96f6c4df5a9a1a233c8fd as the cause of the problems

when adding compatibility-flags no-keyinfo-cache to gpgsm.conf, things work correctly

Event Timeline

• TobiasFella created this task.
• TobiasFella updated the task description. (Show Details)

Was fixed last Thursday with commit rG69a8aefa5bf77136b77383b94e34ba784c1cce89 for 2.2 and will soon make it to master.

• werner claimed this task.

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.

I'm still seeing the same problems both with current master and 2.2

Was fixed in master with rG374195e741cf1c52daad6c07799d308c8a9f73e3 (bug tag was missing in the commit).

@TobiasFella: I don't know why you see the problem in 2.2 - which version on on which platform did you test this.

Is that really the same bug? I would be interested in seeing a more detailed report. BTW, Windows or Linux? Used standard beta installer on Windows?