From: "James Sadler" <freshtonic@gmail.com>
To: git@vger.kernel.org
Subject: Committer authentication in git-send-pack/git-receive-pack
Date: Mon, 24 Mar 2008 15:01:56 +1100 [thread overview]
Message-ID: <e5e204700803232101l431919e0ic8e9fb10c18867d2@mail.gmail.com> (raw)
A while ago, there was some discussion about authenticating commits
using gnupg signatures.
(see http://kerneltrap.org/mailarchive/git/2008/1/29/634209).
I have searched through all of the branches in the main git repo and I
can't see any commits relating to this functionality, so I was
wondering if the work had stalled or perhaps not even been started.
If that's the case, I'm willing to give it a shot and would welcome
some discussion on how to get started.
The posts in the aforementioned thread expand upon the concept beyond
mere authentication and into full audit trail territory. It sounds
like a significant chunk of work.
However, the first logical step (at least to me!) would be to extend
git-send-pack and git-receive-pack to sign and verify communications.
git-send-pack could be extended with a '--sign' argument. This should
produce a signature generated by passing the 'command' part of the
git-send-pack output through to gpg. The rest of the pack need not be
signed, as the SHA-1s in the command section already are
cryptographically associated with the pack itself.
At the other end, git-receive-pack would need to be invoked in such a
way that it knows only to accept signed communications, and where to
find a list of public keys that will be used to authenticate the data.
It will check that the committer's key is known and that the signature
matches the command section generated by send-pack. If the
communication is not signed, or committer is unknown or it fails
verification for any reason, git-receive-pack should die with an
appropriate message.
>From this starting point, other features (discussed in aforementioned
thread) could eventually be added.
Thoughts/advice/opinions/critique welcome.
--
James
reply other threads:[~2008-03-24 4:02 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=e5e204700803232101l431919e0ic8e9fb10c18867d2@mail.gmail.com \
--to=freshtonic@gmail.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).