#Meltdown and #Spectre #Linux #Kernel Status - Update http://www.tuxmachines.org/node/108295
Notices tagged with meltdown, page 2
-
Tux Machines (tuxmachines@mastodon.technology)'s status on Friday, 19-Jan-2018 11:57:11 EST Tux Machines -
Dr. Roy Schestowitz (罗伊) (schestowitz@gnusocial.de)'s status on Wednesday, 17-Jan-2018 21:47:10 EST Dr. Roy Schestowitz (罗伊) #LinuxLite Developer Creates Automated #Spectre #Meltdown Checker for Linux OSes https://gnusocial.de/url/4785020 #gnu #linux -
Nuntius (nuntius@mastodon.club)'s status on Tuesday, 16-Jan-2018 07:04:21 EST Nuntius @lx It's probably gonna be some time until we see fixes. Spectre's apparently hard to exploit, but also hard to fix:
See http://kroah.com/log/blog/2018/01/06/meltdown-status/
TLDR: Numerous patches on the mailing lists, some don't even build, kernel devs worked on #Meltdown first, had no real info in #Spectre, no upstream fixes yetIn conversation from mastodon.club permalink -
Dr. Roy Schestowitz (罗伊) (schestowitz@gnusocial.de)'s status on Monday, 15-Jan-2018 11:52:46 EST Dr. Roy Schestowitz (罗伊) An update on ongoing #Meltdown and #Spectre work https://fedoramagazine.org/update-ongoing-meltdown-spectre-work/ #redhat #fedora #security In conversation from gnusocial.de permalink Attachments
-
Tobias Schmidl 🇪🇺 (schtobia@gnusocial.de)'s status on Friday, 12-Jan-2018 05:50:01 EST Tobias Schmidl 🇪🇺 Nice summary for #meltdown and #spectre mitigation under #debian and #ubuntu https://tms.pw/2D6FgTS In conversation from gnusocial.de at 48°16'7"N 10°50'1"E permalink Attachments
-
clacke (clacke@social.heldscal.la)'s status on Thursday, 11-Jan-2018 21:09:05 EST clacke 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_areIn conversation from social.heldscal.la permalink Attachments
-
ToniQ.es (coloco@quitter.es)'s status on Thursday, 11-Jan-2018 09:12:29 EST ToniQ.es Cómo saber si tu #Linux es vulnerable a los fallos de seguridad #Meltdown y #Spectre https://quitter.es/url/1441630 …#GNULinux In conversation from quitter.es permalink Attachments
-
clacke (clacke@social.heldscal.la)'s status on Thursday, 11-Jan-2018 04:09:41 EST clacke #meltdown #spectre which chips are affected?
/via https://mipump.es/dana/image/yPhBTrL9Qqi23g7CMuO6EQ https://social.heldscal.la/attachment/1213411In conversation from social.heldscal.la permalink -
r҉ustic cy͠be̸rpu̵nk🤠🤖 (cypnk@mastodon.social)'s status on Wednesday, 10-Jan-2018 20:16:08 EST r҉ustic cy͠be̸rpu̵nk🤠🤖 This seems like a fine time to remind people that Ben Eater made an entire video series on building an 8-bit programmable computer from simple TTL chips (including detailed explanations of logic gates)
Best of all, it's #Meltdown and #Spectre proof
https://www.youtube.com/watch?v=HyznrdDSSGM&list=PLowKtXNTBypGqImE405J2565dvjafglHU
In conversation from mastodon.social permalink -
nailyk (nailyk@mstdn.fr)'s status on Wednesday, 10-Jan-2018 07:24:17 EST nailyk Vu sur touiteur (spa moi!)
In conversation from mstdn.fr permalink -
clacke (clacke@social.heldscal.la)'s status on Wednesday, 10-Jan-2018 06:57:36 EST 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)
> wheezy, jessie, jessie-backports, stretch and unstable/sid are fixed
#spectre
> Mozilla has started mitigating Spectre in Firefox and some of these changes are now in Debian unstable (version 57.0.4-1). Chromium has also started mitigating Spectre but no such changes have landed in Debian yet.
https://www.decadent.org.uk/ben/blog/meltdown-and-spectre-in-debian.html
/via https://identi.ca/valhalla/note/vw314uRLQEWJlv0VKoxoTAIn conversation from social.heldscal.la permalink -
Tux Machines (tuxmachines@mastodon.technology)'s status on Wednesday, 10-Jan-2018 06:18:39 EST Tux Machines Ubuntu Releases Security Patch For #Meltdown http://www.tuxmachines.org/node/108030
In conversation from mastodon.technology permalink -
Greg Slepak 🐢 (taoeffect@mastodon.social)'s status on Wednesday, 10-Jan-2018 03:43:21 EST Greg Slepak 🐢 RT https://twitter.com/enisa_eu/status/950773337361403904
Which are the main differences between #Meltdown and #Spectre? #ENISA looks into the critical processor vulnerabilities in new #cybersecurity infonote https://www.enisa.europa.eu/publications/info-notes/meltdown-and-spectre-critical-processor-vulnerabilities
https://mastodon.social/media/CqH-CJ9ZTN_WE42XKJ0In conversation from mastodon.social permalink -
lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Tuesday, 09-Jan-2018 20:47:35 EST lnxw48a1 Someone at work claims #MSFT pulled its #Meltdown / #Spectre patches back for reworking. He said some #AMD systems were bricked by the original patches. #B0rken In conversation from nu.federati.net permalink -
Greg Slepak 🐢 (taoeffect@mastodon.social)'s status on Tuesday, 09-Jan-2018 15:13:25 EST Greg Slepak 🐢 RT https://twitter.com/patrickwardle/status/950811919178383360
if you're interested in the actual impact of Apple's #Meltdown patches, this is the blog to read! 🍎👾
In conversation from mastodon.social permalink -
Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 08-Jan-2018 10:40:59 EST Stéphane Bortzmeyer « Il semblerait toutefois que certains correctifs système ne puissent être installés sans créer des problèmes de compatibilité avec d'autres logiciels, notamment des antivirus. » (Note d'un CERT à propos de #Meltdown) L'antivirus n'était qu'inutile, il devient maintenant une gêne.
In conversation from mastodon.gougere.fr permalink -
silverwizard (silverwizard@friendica.obscuritus.ca)'s status on Monday, 08-Jan-2018 09:30:05 EST silverwizard Suing people for having vulnerabilities always bothers me. Equifax should be hammered HARD - they made a big pile of PII and then were negligent. But Intel found out a thing had unexpected consequences. How do you separate those ideas?
♲ @Ars Technica (arstechnica@twitter.com): After the security flaws became public, maybe we all could've predicted this #Meltdown #Spectre https://arstechnica.com/gadgets/2018/01/intel-faces-class-action-lawsuits-regarding-meltdown-and-spectre/In conversation from friendica.obscuritus.ca permalink -
Zatnosk :blobwizard_sun: (zatnosk@manowar.social)'s status on Monday, 08-Jan-2018 09:06:40 EST Zatnosk :blobwizard_sun: 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 says.
And now everyone is hurting, because we told computers to do stuff we didn't ask them to.
In conversation from manowar.social permalink -
peter hessler @openbsd (phessler@bsd.network)'s status on Monday, 08-Jan-2018 08:40:40 EST peter hessler @openbsd I'm currently super pissed off at #Intel/#Linux/#Microsoft.
So many of the shipping "fixes" for #Meltdown and #Spectre are causing noticeable problems such as "programs aren't starting" and "things take 30x longer".
I'm afraid this will kick off another round of "nobody should install updates!" We had *just* gotten out of that habit :/.
In conversation from bsd.network permalink -
ccc (ccc@quitter.se)'s status on Monday, 08-Jan-2018 06:59:31 EST ccc Das BSI, das uns schon immer gewarnt haben will: Zuständige Behörde erweist sich als Totalausfall http://short1.link/ey9s5v #Meltdown In conversation from quitter.se permalink Attachments