Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: merging pull requests
Date: Fri, 1 Oct 2021 19:35:07 -0700	[thread overview]
Message-ID: <202110011907.6526BCD1@keescook> (raw)
In-Reply-To: <20211001171942.oyq7qtly64tyqi72@nitro.local>

On Fri, Oct 01, 2021 at 01:19:42PM -0400, Konstantin Ryabitsev wrote:
> I don't want to wander too far down that path at the moment, but it's perhaps
> something to consider in the future. With patatt in-header signatures, you
> *can* perform attestation if each commit includes a Link: to the original
> patch message (and that message is cryptographically attested).

Yeah, just getting more folks using patatt would be a great next step. :)

I've proposed adding "patatt validate"[1] to the netdev CI[2], maybe
gfx-ci[3], and others could do the same?

-Kees

[1] https://github.com/kuba-moo/nipa/pull/5
[2] https://github.com/kuba-moo/nipa
    e.g. https://patchwork.kernel.org/project/netdevbpf/patch/20211002003706.11237-3-xiyou.wangcong@gmail.com/
[3] https://patchwork.freedesktop.org/project/intel-gfx-trybot/series/?ordering=-last_updated
    e.g. https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/411177

-- 
Kees Cook

  reply	other threads:[~2021-10-02  2:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 17:33 merging pull requests Kees Cook
2021-09-30 20:00 ` Konstantin Ryabitsev
2021-09-30 23:09   ` Kees Cook
2021-09-30 23:22     ` Stephen Rothwell
2021-09-30 23:29       ` Kees Cook
2021-09-30 23:29     ` Stephen Rothwell
2021-09-30 23:42       ` Kees Cook
2021-10-01 11:59         ` Jason Gunthorpe
2021-10-02  0:15           ` Kees Cook
2021-10-01 17:01         ` Steven Rostedt
2021-10-01 17:07         ` James Bottomley
2021-10-02  0:17           ` Kees Cook
2021-10-01 17:19         ` Konstantin Ryabitsev
2021-10-02  2:35           ` Kees Cook [this message]
2021-09-30 23:31     ` Olof Johansson
2021-10-01  0:09       ` Kees Cook
2021-10-01  0:27         ` Olof Johansson
2021-10-01 17:05           ` Steven Rostedt
2021-10-02  0:12             ` Kees Cook
2021-10-01 18:26     ` Konstantin Ryabitsev
2021-10-01 18:47       ` Linus Torvalds
2021-10-01 19:30         ` Konstantin Ryabitsev
2021-10-02  0:08           ` Kees Cook
2021-10-02  6:22         ` Willy Tarreau
2021-10-02  0:11       ` Kees Cook

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=202110011907.6526BCD1@keescook \
    --to=keescook@chromium.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=sfr@canb.auug.org.au \
    --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