[MODERATED] Re: LVI

[Greg KH <gregkh@linuxfoundation.org>]

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