Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
bw123 wrote:I read another blurb somewhere or other that some of the atom processors might be exempt from one issue or the other. I have one of those on my netbook that I use online, so if anybody runs across any actual info that hasn't signed any non-disclosures or retaineded an attorney, or sells clicks as news, let me know...
I'd be interested in to know as well. My netbook runs an Atom, I just updated the kernel in Slackware from 4.4.14 to 4.4.88 - though apparently it needs to be at least 4.4.109. It would be good if it doesn't affect Atoms, since they can take a while to do things.
Lysander wrote:Haven't done anything to my Debian box yet though
Debian stable has the KTPI patch that (mostly) protects against Meltdown, now that 4.9.75 has been released upstream it shouldn't be long before oldstable gets the fix applied; not sure about poor old wheezy though.
stevepusser wrote:
Since the majority opinion is leaning toward that AMD processors aren't exploitable, you could boot with one of the flags to turn off kpti. Liquorix kernels don't seem to enable it for AMD at all, based on what I saw in the 4.14-11 patch.
After a little more research, and reading the changelog I figured out that kpti is auto by default,
and on my amd sempron it is not enabled, I checked like this:
but it *IS* enabled for the notebook with the atom N450, and the dd copy test is about 25-30% slower. Can't tell any difference in actual usage though, machine works like it always has.
Lysander wrote:Haven't done anything to my Debian box yet though
Debian stable has the KTPI patch that (mostly) protects against Meltdown, now that 4.9.75 has been released upstream it shouldn't be long before oldstable gets the fix applied; not sure about poor old wheezy though.
new stable i386 kernel 4.9.65-3+deb9u2 has no any kpti footprints. is anybody knows why?
dilberts_left_nut wrote:This is a technical thread about this issue - not about whether you feel it's necessary or not.
Is everyone on this forum working for an enterprise operation or cloud service provider? Because if not, "technically" this is a low-risk, local, read-only exploit that has not yet even been seen in the wild. My passwords, credit card numbers and personal information is still much safer on my own systems that they are spread across who knows how many vendors, doctors, insurance companies, etc, etc, regardless.
What's all the fuss about?
Nobody would ever ask questions If everyone possessed encyclopedic knowledge of the man pages.
I've been asking myself the same. I mean this has been known and kept hidden since the middle of last year, if not earlier. I assume the lawyers and hotshots and corporations and public relations firms all had their act together, but it was revealed somehow. Now they are scrambling to assure people that everything is okay...
Subject [patch 00/60] x86/kpti: Kernel Page Table Isolation (was KAISER)
This series is a major overhaul of the KAISER patches:
1) Entry code
Mostly the same, except for a handful of fixlets and delta
improvements folded into the corresponding patches
New: Map TSS read only into the user space visible mapping
This is 64bit only, as 32bit needs the TSS mapped RW
Does this support bw123's finding from earlier -- that kpti isn't available for 686? Based on the comment above, it looks like 686 needs only TSS mapped RW. I have no idea how to verify, though.
acewiza wrote:What's all the fuss about?
EDITED: Okay, I had my coffee and realize that my last comment was itself getting off-topic. Opinions really aren't helpful to the original post, and I thought it was obvious from the first post. Maybe a separate thread would be helpful.
Last edited by n_hologram on 2018-01-07 16:20, edited 2 times in total.
bester69 wrote:There is nothing to install in linux, from time to time i go to google searching for something fresh to install in linux, but, there is nothing
This is 64bit only, as 32bit needs the TSS mapped RW
Does this support bw123's finding from earlier -- that kpti isn't available for 686? Based on the comment above, it looks like 686 needs only TSS mapped RW. I have no idea how to verify, though.
No I was unclear I guess. I am testing/using debian's 4.9.0-5-amd64 kernel on two cpus, an amd sempron and an atom n450. the kernel boots by default with kpti disabled for the sempron, enabled for the atom.
acewiza wrote:"technically" this is a low-risk, local, read-only exploit
Yes but javascript executed by your browser is "local", isn't it?
Only as it relates to my right index finger. Sorry, I tend to overlook the large body of users who gleefully click any link that crosses their desktop.
Nobody would ever ask questions If everyone possessed encyclopedic knowledge of the man pages.
n_hologram wrote:EDITED: Okay, I had my coffee and realize that my last comment was itself getting off-topic. Opinions really aren't helpful to the original post, and I thought it was obvious from the first post. Maybe a separate thread would be helpful.
uh, don't look now but this whole thread is in "off-topic" I thought you knew, you started it?
acewiza wrote:
I tend to overlook the large body of users who gleefully click any link that crosses their desktop.
Yeah and with all the publicity, and "experts" who wrote about this, I didn't see one with the common sense to warn people to turn off or filter javascript.
bw123 wrote:I didn't see one with the common sense to warn people to turn off or filter javascript.
Erm, firefox-esr cannot be used as an attack vector[1] (unlike the non-ESR >v57.0.4) and so users of Debian stable can leave their javascript enabled with impunity.
Head_on_a_Stick wrote:...users of Debian stable can leave their javascript enabled with impunity.
That is like saying I know how to swim so I can't die in a car wreck. Being protected on one browser from one attack does not make unrestricted javascript a good idea.
There are many links about the subject, so I'm confused that you haven't heard about it.
Lysander wrote:Haven't done anything to my Debian box yet though
Debian stable has the KTPI patch that (mostly) protects against Meltdown, now that 4.9.75 has been released upstream it shouldn't be long before oldstable gets the fix applied; not sure about poor old wheezy though.
new stable i386 kernel 4.9.65-3+deb9u2 has no any kpti footprints. is anybody knows why?