linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Konstantin Ryabitsev <mricon@kernel.org>
Subject: Re: [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and fixes
Date: Thu, 12 Apr 2018 15:55:34 -0400	[thread overview]
Message-ID: <a59bbc6d-6cd3-9525-33d1-42b186c5b061@linuxfoundation.org> (raw)
In-Reply-To: <20180412154659.29f5c905@gandalf.local.home>


[-- Attachment #1.1: Type: text/plain, Size: 1009 bytes --]

On 04/12/18 15:46, Steven Rostedt wrote:
> On Thu, 12 Apr 2018 14:28:45 -0400
> Steven Rostedt <rostedt@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 rostedt@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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2018-04-12 19:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12  1:53 [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and fixes Steven Rostedt
2018-04-12  1:54 ` [PATCH 2/5] tracing/uprobe: Add support for overlayfs Steven Rostedt
2018-04-12  1:54 ` [PATCH 3/5] trace_uprobe: Use %lx to display offset Steven Rostedt
2018-04-12  1:54 ` [PATCH 4/5] trace_uprobe: Simplify probes_seq_show() Steven Rostedt
2018-04-12  1:54 ` [PATCH 5/5] tracing: Enforce passing in filter=NULL to create_filter() Steven Rostedt
2018-04-12 17:53 ` [PATCH 0/5] [GIT PULL] tracing: A few last minute clean up and fixes Linus Torvalds
2018-04-12 17:58   ` Linus Torvalds
2018-04-12 18:28     ` Steven Rostedt
2018-04-12 19:00       ` Konstantin Ryabitsev
2018-04-12 19:46       ` Steven Rostedt
2018-04-12 19:55         ` Konstantin Ryabitsev [this message]

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=a59bbc6d-6cd3-9525-33d1-42b186c5b061@linuxfoundation.org \
    --to=konstantin@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mricon@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).