[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220413205714.scrrktpq43kzryim@meerkat.local>
Date: Wed, 13 Apr 2022 16:57:14 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Kees Cook <keescook@...omium.org>
Cc: Christophe Leroy <christophe.leroy@...roup.eu>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v2] lkdtm/bugs: Don't expect thread termination without
CONFIG_UBSAN_TRAP
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
Powered by blists - more mailing lists