From: James Nord <jnord@cloudbees.com>
To: git@vger.kernel.org
Subject: [bug report] commit signature validation
Date: Tue, 30 Apr 2024 17:53:19 +0100 [thread overview]
Message-ID: <CAPcEHyfXuTOjkBfhhEwyqYiZroXGyJSSY0tgJCuSsp5PC-cKLA@mail.gmail.com> (raw)
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
reply other threads:[~2024-04-30 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPcEHyfXuTOjkBfhhEwyqYiZroXGyJSSY0tgJCuSsp5PC-cKLA@mail.gmail.com \
--to=jnord@cloudbees.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).