From: Alejandro Colomar <alx.manpages@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Fabian Stelzer <fs@gigacodes.de>,
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:47:41 +0200 [thread overview]
Message-ID: <dd666e99-b0f6-a05a-532d-13bb3428e8b6@gmail.com> (raw)
In-Reply-To: <YrGvQi8kiFf4a/Tk@kroah.com>
[-- Attachment #1.1: Type: text/plain, Size: 1887 bytes --]
Hi Greg,
On 6/21/22 13:45, Greg KH wrote:
> On Tue, Jun 21, 2022 at 01:34:01PM +0200, Alejandro Colomar wrote:
>> 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). :)
>
> They are independent, patatt I use when sending patches, b4 I use when
> accepting patches. If you never have to accept patches, and read the
> mailing lists using the normal way, no need to use b4.
Oh, I do need to accept patches, for the man-pages :)
But for now, the traffic isn't so high as to need to learn b4(1).
But yes, I would like to learn a bit more about it to simplify some things.
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-06-21 11:48 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
2022-06-21 11:45 ` Greg KH
2022-06-21 11:47 ` Alejandro Colomar [this message]
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=dd666e99-b0f6-a05a-532d-13bb3428e8b6@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 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).