Originally posted by oiaohm
View Post
Announcement
Collapse
No announcement yet.
Spectre/Meltdown Mitigations Can Now Be Toggled With Convenient "mitigations=" Option
Collapse
X
-
Originally posted by debianxfce View PostIn terms of written lines, you believers are troll. IBM/Amazon/what ever sermon does not end.
Term troll has nothing to-do with written lines. In fact calling us believers is an action of a troll. In fact a paid troll normally wants to-do the least number of lines possible to get their disruption to work. So if you are going by written lines of a company pay troll attempting to spread a lie your number of posted lines match perfectly debianxfce. Funny how what debianxfce said applies exactly to debianxfce.
Again before posting again do your background research and understand what you are typing. You have already received a warning and avoided being banned. Spreading dangerous miss information on security could end up with you banned.
- Likes 1
Comment
-
Originally posted by debianxfce View Post
The person who configures the kernel already knows that. SE Linux or any other security feature of the Linux kernel do not throw boot errors with a non debug kernel. IBM non pros suggested to include the kernel command line in to the kernel. It should throw the error message when this new value is used, not just;-)
Also, comparing this to SELinux and other security features is very disingenuous. If we're using cars, SELinux would be a wireless entry with a fingerprint scanner on the unlock button and start buttons and no SELinux is just a wireless entry with a regular unlock and start buttons. Not having the mitigations means the fingerprint scanner is potentially useless due to backdoors (pun not intended) being able to be used or that the regular version could be overridden to accept another wireless entry device since the pairing protocol was exploited.
Compering a kernel-level exploit mitigation to a security implementation and acting like they're one and the same...you should really know better...
Comment
-
Originally posted by debianxfce View Post
When it takes a half year to implement simple value to disable it, you do really must believe that IBM/Amazon/what ever code is safe. Welcome to the reality, no computer system connected to the internet is ever 100% safe. That is why you run Clamtk in the ~/cache folder regularly.
Comment
-
Originally posted by UlisesH View PostNo comments on systemd, gnome or wayland this time????
Ugh! this Spectre/Meltdown nonsense could all have been avoided if people stopped playing with toys like systemd, gnome 3 or wayland and got back to real work!
(how was that?)
Comment
Comment