All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [GIT PULL 2nd resend] leaking_addresses updates for 4.15
Date: Mon, 20 Nov 2017 21:31:15 +1100	[thread overview]
Message-ID: <20171120103115.GI7472@eros> (raw)
In-Reply-To: <87k1yrufwj.fsf@concordia.ellerman.id.au>

On Thu, Nov 16, 2017 at 01:16:28PM +1100, Michael Ellerman wrote:
> "Tobin C. Harding" <me@tobin.cc> writes:
> 
> > Clearly I am unable to use email.
> >
> > Adding to CC: Greg, Steve, Paul - kernel developers CC'd on leaking
> > addresses stuff that may know my face.
> >
> > Adding to CC: Michael - closest kernel developer by proximity that I
> > have had direct correspondence with.
> >
> > Adding to CC: Konstantin - previous correspondence re kernel.org tree hosting. 
> >
> > On Tue, Nov 14, 2017 at 02:45:59PM -0800, Linus Torvalds wrote:
> >> On Tue, Nov 14, 2017 at 1:03 PM, Tobin C. Harding <me@tobin.cc> wrote:
> >> >
> >> > I did not sign the tag, it looks like you have not processed this yet.
> >> > Do you want me to re-do the pull request on a signed tag?
> >> 
> >> When pulling from github? Absolutely.
> >
> > Linus I'm not in the web of trust, pulling a tag signed by an _unknown_
> > key is not secure is it? Would it not be better to get into the web of
> > trust first before requesting you pull any code from me.
> 
> Linus will probably respond, but in short it's good to be in the web of
> trust, but until you are it's still worth signing your tags.
> 
> When you do get some signatures on your key, then we'll be able to see
> that all your existing pull requests were really from you.
> 
> At the end of the day what matters is that you send good code over a
> period of time - and whether the Australian Government agrees that your
> name is "Tobin Harding" is somewhat orthogonal to that.
> 
> > Web of trust presents a social problem that I am not versed in. With my
> > limited knowledge I can present the following solutions.
> >
> > 1. Get my key signed at linux.conf.au in January in Sydney.
> 
> Sounds good, maybe we should have a 15 minute key signing slot at the
> kernel miniconf.

I'll contact the organizer.

> > 2. Request a video call with _some_ number of kernel developers to sign
> >    key (suggested by Konstantin).
> > 3. Drive to Canberra and meet face to face with Michael to sign key
> >    (if he would agree to that).
> 
> Yeah if you want to that's no problem, just give me some notice :)

I understand that there is no rush now so driving seems silly. See you
in Sydney.

thanks,
Tobin.

      reply	other threads:[~2017-11-20 10:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 23:04 [GIT PULL 2nd resend] leaking_addresses updates for 4.15 Tobin C. Harding
2017-11-14 21:03 ` Tobin C. Harding
2017-11-14 22:45   ` Linus Torvalds
2017-11-15 21:21     ` Tobin C. Harding
2017-11-16  2:16       ` Michael Ellerman
2017-11-20 10:31         ` Tobin C. Harding [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=20171120103115.GI7472@eros \
    --to=me@tobin.cc \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulmck@linux.vnet.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.