From: Kees Cook <keescook@chromium.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: Looking for help testing patch attestation
Date: Mon, 23 Mar 2020 12:16:27 -0700 [thread overview]
Message-ID: <202003231214.4669C6088@keescook> (raw)
In-Reply-To: <20200318163930.5n545jfsbenc5vyr@chatter.i7.local>
On Wed, Mar 18, 2020 at 12:39:30PM -0400, Konstantin Ryabitsev wrote:
> If you are interested in participating, all you need to do is to install
> the "b4" tool and start submitting and checking patch attestation.
> Please see the following post for details:
>
> https://people.kernel.org/monsieuricon/introducing-b4-and-patch-attestation
>
> With any feedback, please email the tools@linux.kernel.org list in order
> to minimize off-topic conversations on this list.
Thanks for reaching out! I'll be switching to b4 shortly -- I already
incorporated the earlier version of this tool into my workflow. It's very
easy. I recommend everyone else here give it a try if you're regularly
sending patches around by email. :)
-Kees
--
Kees Cook
prev parent reply other threads:[~2020-03-23 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 16:39 Looking for help testing patch attestation Konstantin Ryabitsev
2020-03-23 19:16 ` Kees Cook [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=202003231214.4669C6088@keescook \
--to=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--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