Messages in this thread | | | Date | Wed, 13 Apr 2022 17:01:31 -0400 | From | Konstantin Ryabitsev <> | Subject | Re: [PATCH v2] lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP |
| |
On Wed, Apr 13, 2022 at 06:29:36AM +0000, Christophe Leroy wrote: > I have a [patatt] section in .gitconfig which contains: > signingkey = ed25519:xxxxxxxx > selector = xxxxxxxx (the same value as above) > > What should I do now for you to get the key ? I don't even know where > the key is stored in my computer.
Your key is stored in ~/.local/share/patatt, but you don't really need to do anything, Kees can do the following:
b4 kr --show-keys 363b58690e907c677252467a94fe49444c80ea76.1649704381.git.christophe.leroy@csgroup.eu
For now, this just provides instructions on what to do with the key:
christophe.leroy@csgroup.eu: (unknown) keytype: ed25519 pubkey: HIzTzUj91asvincQGOFx6+ZF5AoUuP9GdOtQChs7Mm0= krpath: ed25519/csgroup.eu/christophe.leroy/20211009 fullpath: /home/user/.local/share/b4/keyring/ed25519/csgroup.eu/christophe.leroy/20211009 --- For ed25519 keys: echo [pubkey] > [fullpath]
So, for Kees to start being aware of your key, he needs to do:
mkdir -p /home/user/.local/share/b4/keyring/ed25519/csgroup.eu/christophe.leroy echo HIzTzUj91asvincQGOFx6+ZF5AoUuP9GdOtQChs7Mm0= > /home/user/.local/share/b4/keyring/ed25519/csgroup.eu/christophe.leroy/20211009
I know this is awkward and clunky right now. Future versions of b4 will streamline keyring management to make it a lot easier, I promise.
-K
| |