From: Jean Delvare <khali@linux-fr.org>
To: Guenter Roeck <guenter.roeck@ericsson.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [GIT PULL] hwmon fixes for 3.1
Date: Wed, 7 Sep 2011 09:28:16 +0200 [thread overview]
Message-ID: <20110907092816.4634b657@endymion.delvare> (raw)
In-Reply-To: <20110907014725.GC22609@ericsson.com>
On Tue, 6 Sep 2011 18:47:25 -0700, Guenter Roeck wrote:
> On Tue, Sep 06, 2011 at 07:16:13PM -0400, Linus Torvalds wrote:
> > Guys, when using some general git hosting site, I really want some
> > proof that you are you. Not just a "please pull".
> >
> > Tell me *why* I should believe that this is a real pull request from
> > the proper source. Otherwise I'll just wait until kernel.org is back
> > to life, where random people can't just create repositories and send
> > email.
>
> sorry, I didn't think that far. You are absolutely right. No idea if and how
> I can prove that I am me. Generate a PGP signature ? Can't everyone do that
> and subsequently claim to be me ? All I represent (technically) is an account
> on kernel.org, which might not even exist anymore.
When you created this account on kernel.org, you used a PGP key to
identify yourself, didn't you? If you sign your message with that key,
then a few people (basically the kernel.org maintainers) will be able
to confirm that you are the same person who had a trusted kernel.org
account. I don't know if Linus has the list though.
What surprises me a little is that I don't have your public key in my
keyring, and I can't seem to be able to find it on public servers
either. You really should push your key to public key servers,
otherwise a signed message from you has no value in general.
Obviously it's a little late now though. The whole idea of trust and
signatures is to keep the level of trust after odd events such as the
kernel.org break-in. For this, keys must have been exchanged, tested
and trusted long before said event happens.
> (...)
> The fixes are not that important and can wait. Please ignore my pull request;
> I'll re-send it after kernel.org is up and running again.
It's getting long :( I wonder how much more time it will take.
--
Jean Delvare
next prev parent reply other threads:[~2011-09-07 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 16:13 Guenter Roeck
2011-09-06 23:16 ` Linus Torvalds
2011-09-07 1:47 ` Guenter Roeck
2011-09-07 7:28 ` Jean Delvare [this message]
2011-09-07 13:50 ` [lm-sensors] " Guenter Roeck
2011-09-07 7:16 ` Jean Delvare
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=20110907092816.4634b657@endymion.delvare \
--to=khali@linux-fr.org \
--cc=guenter.roeck@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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
all inboxes | Powered by JetHome®