From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 05 Mar 2019 22:31:22 -0000 Received: from smtp.ctxuk.citrix.com ([185.25.65.24] helo=SMTP.EU.CITRIX.COM) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1h1Iam-0008Ec-Nk for speck@linutronix.de; Tue, 05 Mar 2019 23:31:21 +0100 Subject: [MODERATED] Re: Starting to go public? References: From: Andrew Cooper Message-ID: <6012d57e-2d94-c82f-72a2-bd64dde65a85@citrix.com> Date: Tue, 5 Mar 2019 22:31:12 +0000 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="5uqdK5BjTzFwfJRoOE4hoYSWcDQ1HwtCo"; protected-headers="v1" To: speck@linutronix.de List-ID: --5uqdK5BjTzFwfJRoOE4hoYSWcDQ1HwtCo Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Content-Language: en-GB On 05/03/2019 20:36, speck for Jiri Kosina wrote: > On Tue, 5 Mar 2019, speck for Andrew Cooper wrote: > >>> Looks like the papers are starting to leak: >>> >>> https://arxiv.org/pdf/1903.00446.pdf >>> >>> yes, yes, a lot of the attack seems to be about rowhammer, but the >>> "spolier" part looks like MDS. >> So Intel was aware of that paper, but wasn't expecting it to go public= >> today. >> >> =3D46rom their point of view, it is a traditional timing sidechannel o= n a >> piece of the pipeline (which happens to be component which exists for >> speculative memory disambiguation). >> >> There are no proposed changes to the MDS timeline at this point. > So this is not the paper that caused the panic fearing that PSF might l= eak=20 > earlier than the rest of the issues in mid-february (which few days lat= er=20 > Intel claimed to have succesfully negotiated with the researches not to= =20 > publish before the CRD)? Correct. The incident you are referring to is a researcher who definitely found PSF, contacted Intel and was initially displeased at the proposed embargo= =2E ~Andrew --5uqdK5BjTzFwfJRoOE4hoYSWcDQ1HwtCo--