linux-kernel - Re: Bricked x86 CPU with software?

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: <5A539529.10290.130FABDC@tim.ml.ipcopper.com>
Date:   Mon, 08 Jan 2018 07:58:33 -0800
From:   "Tim Mouraveiko" <tim.ml@...opper.com>
To:     Pavel Machek <pavel@....cz>
CC:     linux-kernel@...r.kernel.org
Subject: Re: Bricked x86 CPU with software?

> Hi!
> 
> > > Is the sequence available from ring 3, or does it need ring 0?
> > >
> > > Can we get the code? Extraordinary claims and all that...
> > >
> > 
> > I did not test privilege level. Are you suggesting that I put the code out there for everyone to
> > see or what?
> 
> Yes, that's what I'm suggesting.
> 

That would be neither prudent nor practical.

Perhaps you did not consider the consequences. What if it is compatible with your 
processor? Would you send me a handwritten thank you card if that processor stops 
processing? Would you be a happy replacement-sale customer of Intel? I think you did not 
put much thought into why we are talking about it a year later or at all.

Unlike the now-oh-so-scary feature that was in existence for decades, that is only so scary 
because of a "clever" idea to "cloud" host different customers on bare metal, without any 
consideration to their security, this could affect real people not just oh-so-clever computer 
farmers.