From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx3-rdu2.redhat.com ([66.187.233.73] helo=mx1.redhat.com) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fKrRz-0007et-9S for speck@linutronix.de; Mon, 21 May 2018 22:30:35 +0200 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C17D7407574B for ; Mon, 21 May 2018 20:30:28 +0000 (UTC) Received: from washington.bos.jonmasters.org (ovpn-120-238.rdu2.redhat.com [10.10.120.238]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9C3EFBDC2D for ; Mon, 21 May 2018 20:30:28 +0000 (UTC) Subject: [MODERATED] Re: Date/Time? References: <20180519172627.GB1239@kroah.com> <20180521164655.GI17976@kroah.com> <20180521171240.GD14838@char.us.oracle.com> <20180521194255.GA13975@kroah.com> From: Jon Masters Message-ID: <8157a65a-51ec-b866-936e-ba59bdd43d5f@redhat.com> Date: Mon, 21 May 2018 16:30:27 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="QjBPYOla4gU9LHUAHtg11bEi9DZ2jKAnr"; protected-headers="v1" To: speck@linutronix.de List-ID: This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156) --QjBPYOla4gU9LHUAHtg11bEi9DZ2jKAnr Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05/21/2018 03:48 PM, speck for Jiri Kosina wrote: > On Mon, 21 May 2018, speck for Greg KH wrote: >=20 >> Before an hour ago, I didn't know what "keybase" was. Now that I do=20 >> know, I have no idea how in the world anyone submitted kernel patches = >> using it for ARM people to be basing their code on. >=20 > If Thomas wouldn't set up this list, apparently everything would be=20 > happening just on this keybase (whatever that is). I was a bit shocked = in=20 > the early phases indeed. > I find it rather ironic that for discussing stuff that allows external = > websites to steal encryption keys from your browser ... you use ...=20 > *drumroll* ... external website :) Let's skip the FUD tho. It's not a "website". It's an open source end-to-end encrypted chat application. Its purpose was never to share patches anyway, just for coordination of issues (you can attach files, but that was only for convenience). Keybase also wasn't my idea, but I don't have a problem with it as a useful means of getting many parties collaborating on coordinated disclosure (think of it as IRC but with an attempt at actual security that Google, Intel, and others were ok with using). At the same time, it's great tglx setup this list for Linux patch discussion. They aren't both trying to solve the same thing. Specifically on the other arches, at the time they needed to know what to work on, there was no mailing list anyway (this list wasn't setup for v4 specific discussion at that time, so those folks could not have been added to it anyway). They received a copy of the work in progress, by email as well, and were part of the ongoing discussion so did know each time Konrad mentioned an updated patch was available. Various of us also sent copies of the patches. Folks certainly knew who to ping for help. Regardless of how things should or should not be done, folks were certainly well aware that things were coming today, months ago. Jon. --=20 Computer Architect | Sent from my Fedora powered laptop --QjBPYOla4gU9LHUAHtg11bEi9DZ2jKAnr--