Yes it's easy red is bad, green is good, and not already discovered will be reds next, the problem is; times after times, some new red items are discovered. (and the good news; it's for the moment always before a massive impact)
Zombieload
Re: Zombieload
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32
- Head_on_a_Stick
- Posts: 919
- Joined: Sun Mar 17, 2019 3:37 pm
Re: Zombieload
Absence of evidence is not evidence of absence.
mod note: Signature removed, please read the forum rules
- beardedragon
- Posts: 114
- Joined: Wed Mar 27, 2019 11:26 pm
Re: Zombieload
I am sitting on Debian Testing, waiting for you guys to get this straightened out. At least it works without holes in the kernel.beardedragon wrote: ↑Thu May 16, 2019 8:30 pm I give up, I am going to install fresh and not use that kernel.
Rule #1 Backup Everything
Rule #2 Read Rule #1
Rule #2 Read Rule #1
Re: Zombieload
The risk does not warrant such extreme actions. It could also be rhetorically stated why don't all users change to AMD CPUs?beardedragon wrote: ↑Fri May 17, 2019 3:02 pm Why don't you either patch the kernels and upgrade them. or. drop them and advise the rest of the users to do so.
Re: Zombieload
The kernels are already patched and in the repos. The 5.0-16 Liquorix kernel is also not vulnerable, as the checker output told you.beardedragon wrote: ↑Fri May 17, 2019 3:02 pmWhy don't you either patch the kernels and upgrade them. or. drop them and advise the rest of the users to do so.
- beardedragon
- Posts: 114
- Joined: Wed Mar 27, 2019 11:26 pm
Re: Zombieload
Mitigate: To make less severe, intense, harsh, rigorous, painful,Stevo wrote: ↑Fri May 17, 2019 6:09 pmThe kernels are already patched and in the repos. The 5.0-16 Liquorix kernel is also not vulnerable, as the checker output told you.beardedragon wrote: ↑Fri May 17, 2019 3:02 pmWhy don't you either patch the kernels and upgrade them. or. drop them and advise the rest of the users to do so.
etc.; to soften; to meliorate; to alleviate; to diminish;
to lessen; as, to mitigate heat or cold; to mitigate
grief.
[1913 Webster]
That does not look like fixing the problem. Why even bring this up, or, use a topic that the average user would not even read? Sorry, I am probably too cautious, but, the main reason I do not use Windows is they have too many mitigating circumstances and it is a hacker's dream. I quit using Manjaro after years testing and stable because the main designer took a vacation and everything went to pot, The white screen of death was the result of changing something in nvidia they had no reason to change when they upgraded two kernels. Sorry if I offended you.
Rule #1 Backup Everything
Rule #2 Read Rule #1
Rule #2 Read Rule #1
Re: Zombieload
Fixing the problem would Intel recalling and replacing all of its vulnerable CPUs at Intel's expense. Mitigating the problem is patching Linux kernels such that CPU-induced security vulnerabilities can't affect the operating system. It's not Linux's problem, yet they've patched their kernel to prevent Intel's microcode vulnerabilities from being able to be exploited in Linux. That's why it's called a mitigation, not a "fix" or a solution. It's more of a work-around. It effectively fixes the problem, but since the source of the problem is within Intel's microcode that's where an actual "fix" would need to be applied.beardedragon wrote: ↑Fri May 17, 2019 8:36 pmMitigate: To make less severe, intense, harsh, rigorous, painful,Stevo wrote: ↑Fri May 17, 2019 6:09 pmThe kernels are already patched and in the repos. The 5.0-16 Liquorix kernel is also not vulnerable, as the checker output told you.beardedragon wrote: ↑Fri May 17, 2019 3:02 pm
Why don't you either patch the kernels and upgrade them. or. drop them and advise the rest of the users to do so.
etc.; to soften; to meliorate; to alleviate; to diminish;
to lessen; as, to mitigate heat or cold; to mitigate
grief.
[1913 Webster]
That does not look like fixing the problem. Why even bring this up, or, use a topic that the average user would not even read? Sorry, I am probably too cautious, but, the main reason I do not use Windows is they have too many mitigating circumstances and it is a hacker's dream. I quit using Manjaro after years testing and stable because the main designer took a vacation and everything went to pot, The white screen of death was the result of changing something in nvidia they had no reason to change when they upgraded two kernels. Sorry if I offended you.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: Zombieload
Putting the checker into an desktop icon so I can quickly check my different installs or reminds me to check.
ALso the checker get's installed if not already.
ALso the checker get's installed if not already.
Code: Select all
[Desktop Entry]
Version=1.0
# fehlix: 2019-05-18
# file: spectre-meltdown-checker.desktop
# Zombieload thread: https://forum.mxlinux.org/viewtopic.php?p=503075#p503075
#
Type=Application
Name=Spectre and Meltdown Checker
Comment=Spectre and Meltdown mitigation detection tool
Exec=x-terminal-emulator -T "Spectre and Meltdown Checker" -e bash -c '( hash spectre-meltdown-checker 2>/dev/null || sudo apt install spectre-meltdown-checker) && sudo spectre-meltdown-checker | tee >( (echo "[""code]"; cat ; echo "[/""code]" ) | sed "s/\x1b\[[0-9;]*[mGKH]//g" | xsel -ib 2> /dev/null); echo ; gettext -d mx-goodies -s "Report copied to system clipboard" ; CLOSE=$(gettext mx-goodies "Press any key to close"); read -n 1 -s -r -p "$CLOSE "'
Icon=face-devilish
Path=
Terminal=false
StartupNotify=false
Type=Application
Categories=System;
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Zombieload
there's reddit post about home user overreacted about recent vulnerabilites. I agree, but i'm no expert
https://www.reddit.com/r/linux/comments ... rotecting/
in comment shows new 5.0.16 kernal boot option, mitigation.
https://git.kernel.org/pub/scm/linux/ke ... 34329903ff
I got problem update to 4.19 last-time. Need someone help
https://www.reddit.com/r/linux/comments ... rotecting/
in comment shows new 5.0.16 kernal boot option, mitigation.
https://git.kernel.org/pub/scm/linux/ke ... 34329903ff
I got problem update to 4.19 last-time. Need someone help
Code: Select all
System:
Host: mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.2_x64 Continuum March 14 2018
base: Debian GNU/Linux 9 (stretch)
CPU:
Topology: Dual Core model: Intel Core i3 530 bits: 64
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23407
- Head_on_a_Stick
- Posts: 919
- Joined: Sun Mar 17, 2019 3:37 pm
Re: Zombieload
What was the problem, exactly?
You should probably open a new thread for this.
mod note: Signature removed, please read the forum rules