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]
Message-ID: <20171115213156.pw4v4nvrw4whi3nq@gmail.com>
Date:   Wed, 15 Nov 2017 16:31:56 -0500
From:   Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To:     "Tobin C. Harding" <me@...in.cc>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: leaking_addresses script..

On Thu, Nov 16, 2017 at 08:11:24AM +1100, Tobin C. Harding wrote:
>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@...in.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.

Many kernel developers use "Trust on First Use" (TOFU) approach, which 
is not unreasonable -- it's what ssh has been using for the past couple 
of decades. In the end, the goal of tag signing is not to verify your 
*identity* but to verify that Tobin C. Harding from today is the same 
Tobin C.  Harding whose code was reviewed and merged 3 months ago.

>Also, once I get in the web of trust I can apply to get my tree hosted
>on git.kernel.org so you don't have to pull from GitHub.

We have different rules for issuing actual accounts at kernel.org. We 
*do* rely on the web of trust, since I personally have no way of 
verifying who is a real developer and who isn't. Even then, I don't 
really care about your identity as much as I need to have assurances 
from other members of kernel.org that they have worked with you 
previously and they can vouch that you are their fellow kernel 
developer.

-K

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ