IJHack / QtPass / 41503950821

93%

push

github

ConfigDialog: look an unknown signing key up again after an import (#2116)

* ConfigDialog: look an unknown signing key up again after an import

The signer lookup cache kept "gpg does not know this key" for the
dialog's lifetime, so a key imported into the same GPG home while the
dialog was open stayed unknown, and the shared-key warning missed a
subkey that signs as a primary another profile uses. An unknown key
now keeps the keyring's state (size and time of pubring.kbx and
pubring.gpg, taken before gpg runs) and is asked about again once that
changes: one stat per check, not one gpg run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VJygpMUf461yZgfAqwMJ6d
Signed-off-by: Anne Jan Brouwer <brouwer@annejan.com>

* ConfigDialog: notice keyboxd imports too

With use-keyboxd (GnuPG 2.3 and later, the default in a new home since
2.4.1) keys live in public-keys.d/pubring.db, written to its WAL
first, not in pubring.kbx or pubring.gpg. Both are part of the keyring
stamp now; the test runs once per keyring file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VJygpMUf461yZgfAqwMJ6d
Signed-off-by: Anne Jan Brouwer <brouwer@annejan.com>

* ConfigDialog: notice imports into keyrings gpg.conf names

gpg imports into a primary-keyring set in gpg.conf, and keyring adds
more files, neither of them one of the four fixed names. Stamp the
files those options name too, resolved like gpg resolves them: a bare
name in the GnuPG home, "~/" in the home directory, any other path as
written.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VJygpMUf461yZgfAqwMJ6d
Signed-off-by: Anne Jan Brouwer <brouwer@annejan.com>

* ConfigDialog: ask about unknown keys again on return, not per file

Watching keyring files means guessing gpg's layout: the registry home
on Windows, gpg.conf-2.4 and the system configura... (continued)

9 of 9 new or added lines in 1 file covered. (100.0%)

10098 of 10892 relevant lines covered (92.71%)

398.03 hits per line