Notices tagged with meltdown

grmpyoldman

#Spectre & #Meltdown: Exploiting modern microarchitectures https://fosdem.org/2018/schedule/event/closing_keynote/ #FOSDEM

clacke lobsters

Intel: [We just rushed out some microcode updates out the door to fix the #meltdown thing. Please don't use them.]

https://archive.fo/8GYP0

/via @lobsters https://lobste.rs/s/dy87wk/intel_warns_its_patches_for_chip_flaws_are

clacke

#meltdown #spectre which chips are affected?

/via https://mipump.es/dana/image/yPhBTrL9Qqi23g7CMuO6EQ https://social.heldscal.la/attachment/1213411

clacke

Quick update re: #debian mitigations for the CPU issues: #meltdown > Debian kernel team has worked to mitigate Meltdown in all suites. This mitigation is currently limited to kernels running in 64-bit mode (amd64 architecture) > wheez…

lnxw48a1 rpi , bobjonkman

@bobjonkman Someone posted this explanation earlier: https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/

#meltdown #spectre !rpi

zatnosk

I find it kinda funny how computers are supposed to do exactly what you tell them to, but because SPEEEED, someone told the computers to guess ahead of time what might happen, instead of just doing what the instructions actually …

zatnosk

I find it kinda funny how computers are supposed to do exactly what you tell them to, but because SPEEEED, someone told the computers to guess ahead of time what might happen, instead of just doing what the instructions actually …

lnxw48a1 rpi , bobjonkman

@bobjonkman Someone posted this explanation earlier: https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/

#meltdown #spectre !rpi

stwn

A collection of #Meltdown/#Spectre postings https://lwn.net/Articles/742999/

stwn

A simple explanation of the diffs: #Meltdown vs #Spectre https://danielmiessler.com/blog/simple-explanation-difference-meltdown-spectre/

vinzv gnusocialde

!gnusocialde public service anouncement: In den nächsten Tagen wird es einen kurzen Ausfall geben, um den Server neu zu starten und den #meltdown Patch einzuspielen. Das macht der Provider, weshalb ich keine Kontrolle darüber…

vinzv gnusocialde

!gnusocialde public service anouncement: In den nächsten Tagen wird es einen kurzen Ausfall geben, um den Server neu zu starten und den #meltdown Patch einzuspielen. Das macht der Provider, weshalb ich keine Kontrolle darüber…

espectalll

Here's a nice website explaining the current mess with CPUs, the #Meltdown and #Spectre vulnerabilities https://meltdownattack.com/

espectalll

Here's a nice website explaining the current mess with CPUs, the #Meltdown and #Spectre vulnerabilities https://meltdownattack.com/

grmpyoldman

Dafuq? RT @zigg: CERT recommends throwing away your computer and buying a new one. #meltdown #spectre https://www.kb.cert.org/vuls/id/584653

clacke

#meltdown #spectre https://www.kb.cert.org/vuls/id/584653 > The underlying vulnerability is primarily caused by CPU architecture design choices. Fully removing the vulnerability requires replacing vulnerable CPU hardware. Me: So I gue…

clacke

#meltdown Other methods are being discussed: >> I'm much less worried about these "nospec_load/if" macros, than I am >> about having a sane way to determine when they should be needed. >> >> Is there such a sane model right now, or are…

clacke

#meltdown > The AMD microarchitecture does not allow memory references, including speculative references, that access higher privileged data when running in a lesser privileged mode when that access would result in a page fault. That's…

clacke

#meltdown #spectre #lkml

https://lkml.org/lkml/2018/1/3/780

clacke

#meltdown #spectre #lkml

https://lkml.org/lkml/2018/1/3/780