lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 7 Sep 2011 09:28:16 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Guenter Roeck <guenter.roeck@...csson.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org
Subject: Re: [lm-sensors] [GIT PULL] hwmon fixes for 3.1

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ