From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [GIT PULL] hwmon fixes for 3.1
Date: Wed, 7 Sep 2011 06:50:52 -0700 [thread overview]
Message-ID: <20110907135052.GA26868@ericsson.com> (raw)
In-Reply-To: <20110907092816.4634b657@endymion.delvare>
On Wed, Sep 07, 2011 at 03:28:16AM -0400, Jean Delvare wrote:
[ ... ]
>
> 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.
>
Yeah, one may notice that I am not a security guy and don't pay sufficient
attention to such matters.
> 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.
>
Agreed.
Guenter
next prev parent reply other threads:[~2011-09-07 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 16:13 [GIT PULL] hwmon fixes for 3.1 Guenter Roeck
2011-09-06 23:16 ` Linus Torvalds
2011-09-07 1:47 ` Guenter Roeck
2011-09-07 7:28 ` [lm-sensors] " Jean Delvare
2011-09-07 13:50 ` Guenter Roeck [this message]
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=20110907135052.GA26868@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=khali@linux-fr.org \
--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;
as well as URLs for NNTP newsgroup(s).