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] [day] [month] [year] [list]
Message-ID: <ded3bd8d-3639-0d35-8df3-b63690bdd3b5@intel.com>
Date:   Tue, 21 Jan 2020 10:25:54 -0800
From:   Dave Hansen <dave.hansen@...el.com>
To:     Jan Kiszka <jan.kiszka@...mens.com>,
        Ralf Ramsauer <ralf.ramsauer@...-regensburg.de>,
        Paolo Bonzini <pbonzini@...hat.com>,
        linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Cc:     "Gupta, Pawan Kumar" <pawan.kumar.gupta@...el.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [FYI PATCH 0/7] Mitigation for CVE-2018-12207

On 1/21/20 10:08 AM, Jan Kiszka wrote:
>>> Would be interesting to see this. Ralf and tried something quickly, but
>>> there seems to be a detail missing or wrong.
>>
>> Yep, we still can't reproduce the issue on an affected CPU, and don't
>> know what we miss.
> 
> I just realized that this thread stranded. Ralf told me that he got no
> access to that reproducer which would be very valuable for us right now
> to validate a static mitigation method in Jailhouse. Any chance to get
> the access?

I can't share mine.  Although, if anyone else can share theirs, I can
take a look and make sure that it covers the same cases that mine did.

Does anyone else have a reproducer they can share?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ