From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [RFE] Signing using SSL
Date: Wed, 16 Mar 2022 10:34:05 -0400 [thread overview]
Message-ID: <036701d83942$e6963ca0$b3c2b5e0$@nexbridge.com> (raw)
Following up on our IRC discussion on Monday, I have had a request to
support signing git commits and tags with SSL certificates instead of
SSH/GPG. The organization is heavily invested in SSL infrastructure, so they
want to go down that path.
The basic technique for doing this is, for example:
openssl dgst -sha256 -sign key -out content.sha256 signature.txt -passin
passphrase
There is a pre-step to compute the sha256, in this example, into a file
provided to openssl. We could use openssl to compute the hash also.
Verification is a bit different than what SSH or GPG does:
openssl dgst -sha256 -verify <(openssl x509 -in certificate -pubkey -noout)
-signature sign.txt.sha256 signature.txt
and reports either
Verified OK
Or
Verification Failure
It does not look like completion codes are consistently involved.
This also does look structurally different than both GPG and SSH and more
work to set up. It may be possible to provide wrappers and pretend we are in
SSH, but I'm not sure that is the right path to take.
Any pointers on how this might be done in existing git infrastructure, or
should I look into making this work in code? Sorry to say that the
documentation is not that clear on this.
Thanks in advance,
Randall
--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.
next reply other threads:[~2022-03-16 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 14:34 rsbecker [this message]
2022-03-16 14:49 ` [RFE] Signing using SSL rsbecker
2022-03-16 16:27 ` Fabian Stelzer
2022-03-16 16:44 ` rsbecker
2022-03-29 15:44 ` rsbecker
2022-03-29 17:25 ` 'Fabian Stelzer'
2022-03-29 17:35 ` rsbecker
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='036701d83942$e6963ca0$b3c2b5e0$@nexbridge.com' \
--to=rsbecker@nexbridge.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 NNTP newsgroup(s).