Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4 v0.7.0 is available
Date: Thu, 27 May 2021 12:19:58 +0200	[thread overview]
Message-ID: <YK9yTmBvxymXCzOa@kroah.com> (raw)
In-Reply-To: <20210526192558.pex7tuorwqvkzxe3@nitro.local>

On Wed, May 26, 2021 at 03:25:58PM -0400, Konstantin Ryabitsev wrote:
> ## Patch attestation
> 
> This version includes what I hope is the final rewrite of patch attestation
> features, which has largely moved into its own tool and library called
> "patatt": 
> 
>     https://pypi.org/project/patatt/
> 
> Patatt allows for end-to-end cryptographic attestation of patches via a
> separate X-Developer-Signature email header that is very similar to DKIM. If
> you have an hour, you can see my presentation to OpenSSF Digital Attestation
> WG here:
> https://www.youtube.com/watch?v=no6r1iUqY1A
> 
> B4 will check for this header in the messages it retrieves and will invoke
> patatt (if found) to perform the attestation check, e.g.:
> 
>     $ b4 am -o/tmp 20210521184811.617875-1-konstantin@linuxfoundation.org
>     [...]
>     Checking attestation on all messages, may take a moment...
>     ---
>       ✓ [PATCH 1/3] Sign Message-Id header if present
>       ✓ [PATCH 2/3] Make header order deterministic
>       ✓ [PATCH 3/3] Release as 0.4.0
>       ---
>       ✓ Signed: openpgp/konstantin@linuxfoundation.org
>       ✓ Signed: DKIM/linuxfoundation.org
>     ---
>     [...]
> 
> It is very easy to start signing patches with patatt, so I invite everyone to
> test it out. If you are using git-send-email, you can automate the whole thing
> to happen behind the scenes via the sendemail-validate hook:
> https://pypi.org/project/patatt/#getting-started-as-contributor

Hey, it "just works!":

	Looking up https://lore.kernel.org/r/20210527101426.3283214-1-gregkh%40linuxfoundation.org
	Grabbing thread from lore.kernel.org/linux-usb/20210527101426.3283214-1-gregkh%40linuxfoundation.org/t.mbox.gz
	Analyzing 1 messages in the thread
	Checking attestation on all messages, may take a moment...
	---
	  ✓ [PATCH] USB: gr_udc: remove dentry storage for debugfs file
	  ---
	  ✓ Signed: openpgp/gregkh@linuxfoundation.org
	  ✓ Signed: DKIM/linuxfoundation.org
	---
	Total patches: 1
	---
	 Link: https://lore.kernel.org/r/20210527101426.3283214-1-gregkh@linuxfoundation.org
	 Base: not found (applies clean to current tree)
	Applying: USB: gr_udc: remove dentry storage for debugfs file


Nice job!

greg k-h

      parent reply	other threads:[~2021-05-27 10:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 19:25 b4 v0.7.0 is available Konstantin Ryabitsev
2021-05-26 19:41 ` Jason Gunthorpe
2021-05-26 19:56   ` Konstantin Ryabitsev
2021-05-26 19:58     ` Konstantin Ryabitsev
2021-05-26 20:52     ` Jason Gunthorpe
2021-05-27  7:56 ` Geert Uytterhoeven
2021-05-27 12:00   ` Konstantin Ryabitsev
2021-05-27 12:05     ` Geert Uytterhoeven
2021-05-27 13:19       ` Konstantin Ryabitsev
2021-05-27 10:19 ` Greg KH [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=YK9yTmBvxymXCzOa@kroah.com \
    --to=greg@kroah.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    --cc=users@linux.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