Hi, reporting bug per https://git-scm.com/community (also this is not specific to windows and has been reporoduced on OSX) Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) Setup git commit signing with SSH (but omit setting gpg.ssh.allowedsignersfile) create a signed comment run git show --show-signature What did you expect to happen? (Expected behavior) the commit should show an unverified signature What happened instead? (Actual behavior) the commit shows no signature what so ever What's different between what you expected and what actually happened? I would expect show to say there is a signature that it could not verify, instead the output is seemingly telling me there is no signature at all. Anything else you want to add: this also occurs if pulling from a repo where someone else has enabled signing with ssh, but you have not configured `gpg.ssh.allowedsignersfile` Regardless of the presence of the signing file git should tell me there is an unverified signature. Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.44.0.windows.1 cpu: x86_64 built from commit: ad0bbfffa543db6979717be96df630d3e5741331 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 22631 compiler info: gnuc: 13.2 libc info: no libc information available $SHELL (typically, interactive shell): <unset> [Enabled Hooks] not run from a git repository - no hooks to show
