Re: VMM vulns?

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAl9aVyoACgkQsoi1X/+c
IsG3xRAAm83w1RBSm4gN2IzGA3tAh0MetfswnWBsfizBLRW0PzqoGBgtnbMFAwB9
i41AxYcnR4/ihLstUtX0ul8dcPCm+F7p2sMNuSAKCMDN/NIhYvYZRwpm9BHYWoJf
5vdtCsB9O9lntm5iwNRSzwANUE6FAjUumB2Da1i74alU9sbpew3mLPg0B+NPaQRV
jw18XBYOMTvPra/PZKURvoitPs+lm9I6+W9jto0JeoxCxUYx2lbPcTQrFOUNfSdT
nnO5LHtZCtoHpjbQ6IEYyAkfbp59HF3gEOtbvHtJ3RFP8jLIQ6O17UwoEC0sNwLH
BsZwZU+0CeT40okXooXcjCdr+BVr0eCZdy0sBWwq9Y5TidVGBJmTw0M91bvYAg1Q
Q9HLi2eBSF7K1bNwRvp0Ow1zoqVWnsWkdjyovNDlREBcrHbxOLxOP/OA42ZJi+gR
v/pf/Ng7GNyLhHnzf8xOJ5TYQAt0AG1ZOgyrhzRyB+pzb/DGBchrK3GZt6lcyFDK
HPjWSh1YXdYAj8IjJrQzrMipYQWYjDs0e5Z4nGY9pTr7q7uzRPl4jHMbhVkvvWlP
Cb8muGyY7GW4ysLABgz/1y8O59wMm6HiMPS71FiMP82QvYW7UMWnpV9nRIdaR/G6
yyeoGRzPYxFA7yUok3l0N50Sc0j8+CzzqUgrOTIF8AH+6HH9/Rs=
=cgvl
-----END PGP SIGNATURE-----
On 2020-09-03 01:09, Mike Larkin wrote:
> On Wed, Sep 02, 2020 at 09:36:14PM -0400, Bryan Steele wrote:
>> On Wed, Sep 02, 2020 at 02:03:35AM -0700, Mike Larkin wrote:
>>> On Wed, Sep 02, 2020 at 03:35:54AM +0200, fro@disciples.com wrote:
>>>> https://twitter.com/m00nbsd/status/1291257985734410244
>>>>
>>>> I don't want to bump that old thread or start any arguments about this. I'm just curious if this tweet is accurate or have these issues been addressed? Were any of Maxime's suggestions implemented?
>>>>
>>>
>>> I am not sure if anyone picked up the remaining issues after I left active
>>> vmm development. At that time, I sent out my WIP diff for the TLB flush issue
>>> Maxime reported; it was not 100% complete. I am not sure if anyone is working
>>> on that or not, or any other issues he reported.
>>>
>>> -ml
>>
>> As far as I'm aware all the pvclock(4) issues were addressed by pd@ and
>> mortimer@.
>>
>> https://marc.info/?l=openbsd-cvs&m=158180761313544&w=2
>> https://marc.info/?l=openbsd-cvs&m=158269876318391&w=2
>>
>> The "assorted bugs and vulns" like the RDMSR passthrough and the XSETBV
>> CPL check issues were handled by pd@, me and kettenis@ and they have all
>> been committed.
>>
>> https://marc.info/?l=openbsd-cvs&m=158196338821895&w=2
>>
>> The direct map issue on Intel CPUs hinted at by Maxime was also fixed
>> by kettenis@, deraadt@ and millert@.
>>
>> https://marc.info/?l=openbsd-cvs&m=158269724517998&w=2
>>
>> -Bryan.
>>
>
> The TLB flush issues are still outstanding.
>
> -ml

Yikes! Is https://openbsd.amsterdam affected?

-Demi