From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2] lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP
Date: Wed, 13 Apr 2022 16:57:14 -0400 [thread overview]
Message-ID: <20220413205714.scrrktpq43kzryim@meerkat.local> (raw)
In-Reply-To: <202204121440.FEE123D7@keescook>
On Tue, Apr 12, 2022 at 04:06:20PM -0700, Kees Cook wrote:
> Also, Konstantin, I note that
> https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/
> does not have a .keyring/ed25519 directory. Should it?
No, because it's not a "pgpkey". :)
> I added one
> locally for at least one other developer, as I use this setting:
>
> [patatt]
> keyringsrc = ~/korg/pgpkeys/.keyring
>
> Am I holding this thing wrong? :)
Nope, but you can also list multiple locations where patatt can look, for
example:
[patatt]
keyringsrc = ~/korg/pgpkeys/.keyring
keyringsrc = ~/.local/share/patatt/public
In fact, if you take Christophe's patches all the time, you can add a keyring
ref to your tree. The process is documented here:
https://github.com/mricon/patatt#managing-the-keyring-large-teams
This way I'm not managing the keys of your trusted contributors.
I'll be happy to explain further -- in fact, I'm happy anyone uses it at all!
:)
-K
next prev parent reply other threads:[~2022-04-13 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 19:13 Christophe Leroy
2022-04-12 23:06 ` Kees Cook
2022-04-13 6:29 ` Christophe Leroy
2022-04-13 21:01 ` Konstantin Ryabitsev
2022-04-13 21:20 ` Kees Cook
2022-04-13 20:57 ` Konstantin Ryabitsev [this message]
2022-04-13 21:22 ` 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=20220413205714.scrrktpq43kzryim@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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