From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (193.142.43.55:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 21 Nov 2019 13:45:19 -0000 Received: from mail.kernel.org ([198.145.29.99]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iXmlp-0004O2-38 for speck@linutronix.de; Thu, 21 Nov 2019 14:45:18 +0100 Date: Thu, 21 Nov 2019 14:45:07 +0100 From: Greg KH Subject: [MODERATED] Re: LVI Message-ID: <20191121134507.GA548518@kroah.com> References: <20191119174008.7dbymix2eo4mrv57@treble> <20191120171353.tosbnx6a5rhsnidg@treble> <20191120172529.GA3071146@kroah.com> <20191120190943.GH4097@hirez.programming.kicks-ass.net> <20191120191942.GA3086925@kroah.com> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Thu, Nov 21, 2019 at 01:50:05AM +0100, speck for Thomas Gleixner wrote: > On Wed, 20 Nov 2019, speck for Greg KH wrote: > > On Wed, Nov 20, 2019 at 08:09:43PM +0100, speck for Peter Zijlstra wrote: > > > On Wed, Nov 20, 2019 at 06:25:29PM +0100, speck for Greg KH wrote: > > > > > > > > > > > > What kernel changes (if any) are needed for LVI? I haven't seen any > > > > > > discussion here. > > > > > > > > > > > > The last I heard, the official CRD was Dec 10, but was likely to move to > > > > > > March. > > > > > > > > > > Luckily this has been moved to March 10, 2020. > > > > > > > > It has? Where is this all being tracked? > > > > > > > > Last I saw was a strange presentation with odd dates, can't we have a > > > > "simple" text file in keybase at the very least for this type of thing? > > > > > > Please, no keybase, kill and exterminate that crap. > > > > For sending pictures of people drinking beer, it's fine. For trying to > > talk about technical things, it's horrid. > > > > But, there is a git plugin and there is a repo that uses it, see the > > other email for details on how to clone it. I can live with that for > > basic things like "list of issues / disclosure dates" as long as people > > keep it up to date. > > This requires to have a keybase account in the first place. Which I don't > have and Peter neither. I don't have one because back then when this > keybase thingy started participation was requiring some form of social > media ID (what a retarded security concept) which I don't have. Fair enough, I only remember to log into it when someone mentiones something might have changed. > Just for the record. We are fixing Intel's crap and it's Intel's > repsonsibility to make information accessible to us in ways which do not > force us to use randomly chosen chit-chat infrastructure which happens to > have a git repository associated. Do I have to repeat that forever? I think we do, as it really does not seem to sink in :( > If there is a way to submit a ssh key to get access to that git repository > without telling the farcebooks and gurgles of this world about me, then I > might be in. > > Alternatively I'm happy to give write access to a speck repo branch or a > seperate repo, which is accessible to this group by old fashioned, but > halfways trustable technology, to someone who volunteers to sync that > stuff. I think an Intel person should do this if they wish to use keybase to try to hold things we are supposed to be paying attention to. greg k-h