From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org
Subject: in-header PGP patch attestation in latest master
Date: Mon, 23 Nov 2020 15:58:42 -0500 [thread overview]
Message-ID: <20201123205842.owomj4qojgjmtjzr@chatter.i7.local> (raw)
Hi, all:
The latest master implements in-header PGP attestation, following my
ongoing work on that subject. I am now convinced that my initial
attestation implementation via detached "certification documents" is not
sufficiently fault-tolerant due to requiring access to lore.kernel.org
for verification, so I'm moving on to in-header attestation in hopes to
come up with a better scheme that doesn't require any central
infrastructure pieces for verification purposes.
You can read more about my proposal here:
https://git.kernel.org/pub/scm/linux/kernel/git/mricon/patch-attestation-poc.git/tree/README.rst
The latest b4 implements the PGP attestation mode both for generating
and attesting patch signatures. If you would like to trial it out, the
easiest way to enable it is via git's sendemail-validation hook and is
described in the README:
https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/README.rst#n33
Please let me know if it's working for you or not.
-K
reply other threads:[~2020-11-23 20:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201123205842.owomj4qojgjmtjzr@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=tools@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;
as well as URLs for NNTP newsgroup(s).