-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Rusty Bird:
> To me as a layman, it looks like Qubes is indeed vulnerable to the
> XSA-273 data leak, and that fixing it involves
>
> 1. disabling hyperthreading (by adding smt=off to the Xen command line)
> 2. AND upgrading Intel microcode to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Chris Laprise:
> On 08/15/2018 08:40 AM, Rusty Bird wrote:
> > To me as a layman, it looks like Qubes is indeed vulnerable to the
> > XSA-273 data leak, and that fixing it involves
> >
> > 1. disabling hyperthreading (by adding smt=off to the Xen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sphere:
> I have hyperthreading disabled on my BIOS, do I still have to add
> that option to Xen command line?
Disabling it in the BIOS is okay too, according to the XSA.
> By pull request you mean, it's still being grabbed for use and
>
On 08/15/2018 08:40 AM, Rusty Bird wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sphere:
https://www.bleepingcomputer.com/news/security/researchers-disclose-new-foreshadow-l1tf-vulnerabilities-affecting-intel-cpus/
There are other vulnerabilities disclosed along with this today and
On Wednesday, August 15, 2018 at 8:50:28 PM UTC+8, Rusty Bird wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Sphere:
> > https://www.bleepingcomputer.com/news/security/researchers-disclose-new-foreshadow-l1tf-vulnerabilities-affecting-intel-cpus/
> >
> > There are other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sphere:
> https://www.bleepingcomputer.com/news/security/researchers-disclose-new-foreshadow-l1tf-vulnerabilities-affecting-intel-cpus/
>
> There are other vulnerabilities disclosed along with this today and
> if possible, I would like to confirm
https://www.bleepingcomputer.com/news/security/researchers-disclose-new-foreshadow-l1tf-vulnerabilities-affecting-intel-cpus/
There are other vulnerabilities disclosed along with this today and if
possible, I would like to confirm that as well.
On a side note, I have long disabled
