On 04/12/18 15:46, Steven Rostedt wrote: > On Thu, 12 Apr 2018 14:28:45 -0400 > Steven Rostedt <rost...@goodmis.org> wrote: > >> Primary key fingerprint: 5ED9 A48F C54C 0A22 D1D0 804C EBC2 6CDB 5A56 DE73 >> Subkey fingerprint: B5D7 BDD5 67E0 67A3 EE0C 9FBE 3F0B D661 FC59 E3D3 > > Don't use this key. > > Konstantin wanted me to make a ECC key, which I did. Here's the new key: > > Subkey fingerprint: 514B 0EDE 3C38 7F94 4FB3 7993 29E5 7410 9AEB FAAA
Nice! You don't actually have to tell people the fingerprint, as the subkey will inherit the trust/validity of your master key. For the recipients, it's sufficient to just refresh your key: gpg2 --refresh-key rost...@goodmis.org To validate ECC tags, you will need to tell git to always use gpg2, since gpg1 doesn't know what ECC is: git config --global gpg.program gpg2 git config --global gpgv.program gpgv2 Regards, -- Konstantin Ryabitsev Director, IT Infrastructure Security The Linux Foundation
signature.asc
Description: OpenPGP digital signature
