https://zombieloadattack.com/
https://zombieloadattack.com/zombieload.pdf
https://www.cyberus-technology.de/posts/2019-05-14-zombieload.html
https://github.com/IAIK/ZombieLoad
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018
On Wed, May 15, 2019 at 03:24:54AM -0400, grarpamp wrote:
> https://zombieloadattack.com/
> https://zombieloadattack.com/zombieload.pdf
> https://www.cyberus-technology.de/posts/2019-05-14-zombieload.html
> https://github.com/IAIK/ZombieLoad
> https://github.com/intel/Intel-Linux-Processor-Microcod
> New CPU microcode may be available in a BIOS update from your system vendor,
> or by installing the devcpu-data package or sysutils/devcpu-data port.
> Ensure that the BIOS update or devcpu-data package is dated after 2014-05-14.
>
> If using the package or port the microcode update can be appli
On 5/15/2019 8:18 AM, Wall, Stephen wrote:
>> New CPU microcode may be available in a BIOS update from your system vendor,
>> or by installing the devcpu-data package or sysutils/devcpu-data port.
>> Ensure that the BIOS update or devcpu-data package is dated after 2014-05-14.
>>
>> If using the pa
> On 15 May 2019, at 15:32, mike tancsa wrote:
>
> Actually, just tried this on RELENG_11 (r347613) and I get
>
> don't know how to load module '/boot/firmware/intel-ucode.bin'
>
> In boot/loader.conf I have
>
> cpu_microcode_load="YES"
> cpu_microcode_name="/boot/firmware/intel-ucode.bin”
On 15.05.19 14:18, Wall, Stephen wrote:
New CPU microcode may be available in a BIOS update from your system vendor,
or by installing the devcpu-data package or sysutils/devcpu-data port.
Ensure that the BIOS update or devcpu-data package is dated after 2014-05-14.
If using the package or port t
cpu_microcode_load="intel-ucode”
Don’t remember that as needing to be yes but could be wrong.
--
J. Hellenthal
The fact that there's a highway to Hell but only a stairway to Heaven says a
lot about anticipated traffic volume.
> On May 15, 2019, at 08:32, mike tancsa wrote:
>
> cpu_microcod
On 5/15/2019 10:27 AM, Borja Marcos wrote:
>
>> On 15 May 2019, at 15:32, mike tancsa wrote:
>>
>> Actually, just tried this on RELENG_11 (r347613) and I get
>>
>> don't know how to load module '/boot/firmware/intel-ucode.bin'
>>
>> In boot/loader.conf I have
>>
>> cpu_microcode_load="YES"
>> cpu
> On 15 May 2019, at 16:33, mike tancsa wrote:
>
>> on /etc/rc.conf with the devcpu-data port installed and as far as I know it
>> updated the microcode.
>>
>> The script in /usr/local/etc/rc.d used cpucontrol(8) to load it.
>>
>> Or am I holding it wrong?
>
> Supposedly 2 ways to do it. W
On Wed, May 15, 2019 at 09:33:50AM -0500, Kyle Evans wrote:
> On Wed, May 15, 2019 at 8:33 AM mike tancsa wrote:
> >
> > On 5/15/2019 8:18 AM, Wall, Stephen wrote:
> > >> New CPU microcode may be available in a BIOS update from your system
> > >> vendor,
> > >> or by installing the devcpu-data pa
On Wed, May 15, 2019 at 8:33 AM mike tancsa wrote:
>
> On 5/15/2019 8:18 AM, Wall, Stephen wrote:
> >> New CPU microcode may be available in a BIOS update from your system
> >> vendor,
> >> or by installing the devcpu-data package or sysutils/devcpu-data port.
> >> Ensure that the BIOS update or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
=
FreeBSD-SA-19:07.mdsSecurity Advisory
The FreeBSD Project
Topic:
El mié., 15 may. 2019 13:06, Peter Pentchev escribió:
> On Wed, May 15, 2019 at 03:24:54AM -0400, grarpamp wrote:
> > https://zombieloadattack.com/
> > https://zombieloadattack.com/zombieload.pdf
> > https://www.cyberus-technology.de/posts/2019-05-14-zombieload.html
> > https://github.com/IAIK/Zo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
=
FreeBSD-SA-19:07.mdsSecurity Advisory
The FreeBSD Project
Topic:
In message
=?UTF-8?Q?Fernando_Apestegu=C3=ADa?= wrote:
>So, a big applause is in order for the quick response.
+1
Thanks to everyone involved who has labored to try to keep us all safe.
___
freebsd-security@freebsd.org mailing list
https://lists.fr
15 matches
Mail list logo