From: Fabian Stelzer <fs@gigacodes.de>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: send PGP signed commits/patches with git-send-email(1)
Date: Fri, 17 Jun 2022 14:00:16 +0200 [thread overview]
Message-ID: <20220617120016.txjksectzdugqiod@fs> (raw)
In-Reply-To: <81caab7d-777e-13fe-89ea-820b7b2f0314@gmail.com>
On 17.06.2022 12:24, Alejandro Colomar wrote:
>Hi,
>
>In Kernel Recipes this month [1], Greg mentioned that
>git-send-email(1) could be used together with gpg(1) to verify
>authenticity of the sender.
I think he is talking about GPG signing the email containing the patch and
is not referring to git commit signing.
Using GPG to sign your whole email adds trust to a whole lot more than just
the sent patch. It can verify the authenticity of the sender, and all the
rest of the emails content and follow up discussions / review.
Including the commits signature in the email might have some benefit but I'm
not sure about how much. It could decouple the trust of the patches
integrity of the transport used to publish it. For example you could forward
/ copy a patch and the recipient could still verify the original authors
signature.
Konstantin Ryabitsev has done some work in this area especially for kernel
development by using email headers:
https://people.kernel.org/monsieuricon/end-to-end-patch-attestation-with-patatt-and-b4
https://github.com/mricon/patatt
>
>I couldn't find any documentation about it, and if I create a patch
>from a commit that was signed (-S), the PGP signature is not part of
>the patch.
>
>So, is there a way to PGP-authenticate patches?
>If not, could this be added to git(1)?
>
>$ git --version
>git version 2.36.1
>
>Thanks,
>
>Alex
>
>
>[1]: <https://www.youtube.com/watch?v=nhJqaZT94z0>
>
> - Start of thread Q&A in 1:56:30.
> - Greg's answer starts in 1:56:57
> - Specific git-send-email(1) part in 1:57:50
>
>--
>Alejandro Colomar
><http://www.alejandro-colomar.es/>
next prev parent reply other threads:[~2022-06-17 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:24 send PGP signed commits/patches with git-send-email(1) Alejandro Colomar
2022-06-17 12:00 ` Fabian Stelzer [this message]
2022-06-17 12:12 ` Konstantin Ryabitsev
2022-06-21 11:16 ` Greg KH
2022-06-21 11:34 ` Alejandro Colomar
2022-06-21 11:45 ` Greg KH
2022-06-21 11:47 ` Alejandro Colomar
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220617120016.txjksectzdugqiod@fs \
--to=fs@gigacodes.de \
--cc=alx.manpages@gmail.com \
--cc=git@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).