All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Fabian Stelzer <fs@gigacodes.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: send PGP signed commits/patches with git-send-email(1)
Date: Tue, 21 Jun 2022 13:34:01 +0200	[thread overview]
Message-ID: <03af9a8e-cf2c-8a32-330d-debad956683d@gmail.com> (raw)
In-Reply-To: <YrGoqEi3shil7pkM@kroah.com>


[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]

Hi!

On 6/21/22 13:16, Greg KH wrote:
> On Fri, Jun 17, 2022 at 08:12:12AM -0400, Konstantin Ryabitsev wrote:
>> On Fri, Jun 17, 2022 at 02:00:16PM +0200, Fabian Stelzer wrote:
>>> 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
>>
>> Greg refers specifically to patatt signatures. They aren't really specific to
>> kernel development at all -- they can be used for any patches sent via mail.
>>
>> b4 (the tool used by many maintainers to retrieve patches from lists) will
>> check patatt-style signatures (in addition to DKIM signatures) to help verify
>> that the patches come from trusted sources and aren't someone pretending to be
>> someone else.
> 
> Yes, I was referring to patatt here, as linked by Konstantin's blog post
> above.  It's part of the b4 tool (well, a git subproject in it), real
> link is at:
> 	https://git.kernel.org/pub/scm/utils/patatt/patatt.git

Thank you all for the info.
It works like charm (I still need to learn b4(1), but patatt(1) is 
enough for me right now). :)

Cheers,

Alex

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-06-21 11:34 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
2022-06-17 12:12   ` Konstantin Ryabitsev
2022-06-21 11:16     ` Greg KH
2022-06-21 11:34       ` Alejandro Colomar [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=03af9a8e-cf2c-8a32-330d-debad956683d@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=fs@gigacodes.de \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.