lkml.org 
[lkml]   [2022]   [Apr]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2] lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP
On Wed, Apr 13, 2022 at 04:57:14PM -0400, Konstantin Ryabitsev wrote:
> 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!
> :)

I read emails out of order. :) Thanks!

If the expectation is other kernel devs are using ed25519 over gpg,
should there be a central repo for those?

--
Kees Cook

\
 
 \ /
  Last update: 2022-04-13 23:24    [W:0.085 / U:0.376 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site