Intel CPUs Massive Security Flaw issue

[JKnott]

I just came across this:
http://www.pcgamer.com/intel-ceo-sold-39-million-in-company-shares-prior-to-disclosure-of-cpu-security-flaws/

[robi]

This is not a joke anymore. Really.

[ivor]

@robi:

@ivor:

Our preliminary assessment of Meltdown and Spectre vulnerabilities suggests that most pfSense use cases without untrusted local users or a multi-tenant context should not be concerned.

Can you please elaborate a little bit this, so we can understand what you mean? Especially the "most pfSense use cases without untrusted local users or a multi-tenant context ".
The whole pfSense runs as root, including the web interface afaik…

@lra:

@ivor:

Our preliminary assessment of Meltdown and Spectre vulnerabilities suggests that most pfSense use cases without untrusted local users or a multi-tenant context should not be concerned.

Once the FreeBSD project issues a patched release, we will incorporate those patches, test, and release new versions of pfSense.

Engineering question, if the Meltdown and Spectre kernel fixes reduces pfSense performance by 5% or more, is that prudent ?

If Meltdown and Spectre require malicious code running locally, all bets are off, and there are far easier methods to extract credentials.

Bottom line, are the Meltdown and Spectre fixes appropriate for an appliance like pfSense ?

We will know more information once there's a fix in place so I would rather not speculate now. Once the fix is ready, it will be available in snapshots.

[AMD_infinium05]

@ivor:

Our preliminary assessment of Meltdown and Spectre vulnerabilities suggests that most pfSense use cases without untrusted local users or a multi-tenant context should not be concerned.

Once the FreeBSD project issues a patched release, we will incorporate those patches, test, and release new versions of pfSense.

Could you please elaborate/simplify to understand more about this statement?

[robi]

https://github.com/corna/me_cleaner/issues/142

::)

[kpa]

@AMD_infinium05:

@ivor:

Our preliminary assessment of Meltdown and Spectre vulnerabilities suggests that most pfSense use cases without untrusted local users or a multi-tenant context should not be concerned.

Once the FreeBSD project issues a patched release, we will incorporate those patches, test, and release new versions of pfSense.

Could you please elaborate/simplify to understand more about this statement?

The vulnerabilities do not affect pfSense in a usual configuration where there are no local users that could have local execution privileges for untrusted code.

[Gil]

A "Quantum of Solace" for me in that statement - (To coin a phrase)

[bfeitell]

@ivor:

Our preliminary assessment of Meltdown and Spectre vulnerabilities suggests that most pfSense use cases without untrusted local users or a multi-tenant context should not be concerned.

Once the FreeBSD project issues a patched release, we will incorporate those patches, test, and release new versions of pfSense.

This makes sense for PFSense itself, but what about packages like Snort and Suricata that actively evaluate untrusted and malicious code all the time?

[WERTYU]

This post is deleted!

[lra]

@ivor:

@lra:

@ivor:

Our preliminary assessment of Meltdown and Spectre vulnerabilities suggests that most pfSense use cases without untrusted local users or a multi-tenant context should not be concerned.

Once the FreeBSD project issues a patched release, we will incorporate those patches, test, and release new versions of pfSense.

Engineering question, if the Meltdown and Spectre kernel fixes reduces pfSense performance by 5% or more, is that prudent ?

If Meltdown and Spectre require malicious code running locally, all bets are off, and there are far easier methods to extract credentials.

Bottom line, are the Meltdown and Spectre fixes appropriate for an appliance like pfSense ?

We will know more information once there's a fix in place so I would rather not speculate now. Once the fix is ready, it will be available in snapshots.

For Reference …
DragonFlyBSD Lands Fixes For Meltdown Vulnerability
https://www.phoronix.com/scan.php?page=news_item&px=DragonFly-Meltdown-Fixed

"... system call performance is reduced, similar to Linux, when the isolation is enabled. DragonFly reports that system calls go from about 100ns to ~350ns. In typcial workloads they say you should "not lose more than 5% performance or so. System-call heavy and interrupt-heavy workloads (network, database, high-speed storage, etc) can lose a lot more performance."

[kpa]

@bfeitell:

@ivor:

Our preliminary assessment of Meltdown and Spectre vulnerabilities suggests that most pfSense use cases without untrusted local users or a multi-tenant context should not be concerned.

Once the FreeBSD project issues a patched release, we will incorporate those patches, test, and release new versions of pfSense.

This makes sense for PFSense itself, but what about packages like Snort and Suricata that actively evaluate untrusted and malicious code all the time?

No they don't, what they do is they analyze patterns in the incoming and outgoing connections on both the IP headers and the data payload level and then make decisions based on rules if there is an active threat going on. None of their operations involve an actual execution of untrusted program code, it would be just plain crazy if such thing was allowed.

[bimmerdriver]

@Chrismallia:

@KOM:

AMD's performance is so far behind that even 30% slower the Intel is still faster  and I suspect they have their own issues.

From what I have read, AMD's latest Threadripper CPUs are giving Intel a run for their money, and they're cheaper.  As for issues, unless you have something concrete then you can't really make that claim.  I've seen others saying the same thing on other tech forums, that this Intel bug is bad but AMD might maybe perhaps possibly have something as bad or worse.  It's pure FUD.

Sorry to disagree

Threadripper  does nearly half the work clock per cycle  of an Intel  plus they run much hotter and are less power efficient

Work per clock cycle is an irrelevant measurement unless you are comparing similar architectures and even then, while it may be interesting, it still doesn't really matter. The relative performance of AMD vs. Intel depends on the workload. (This applies to Ryzen vs. Core as well as Epyc vs. Xeon.)

Anandtech rated the ThreadRipper as the best overall workstation processor, taking both price and performance into account. Here is a reference: https://www.anandtech.com/show/11891/best-cpus-for-workstations-2017

[jahonix]

@dotdash:

I don't see much of an attack vector on a firewall

What about installs on hypervisors, be it local on, say vmware, or in the cloud at azure or aws?
That's where the fun begins and that's where more valuable data can be sourced from than from your home with a dedicated pfSense machine, right?

[n3by]

Is is possible for pfSense to load updated CPU microcode at kernel boot as in Linux / windows ?

[kejianshi]

Based on what I've read, pfsense users have nothing to worry about if pfsense is installed on a physical machine or if it is installed as a VM along with other virtual appliances on hardware that you own and only you use.

You start having risks when you are one of many subscribers to a cloud service and you have no idea if the other subscribers are running malware that exploits these vulnerabilities.

I'm far more worried that for most of us, the cure will be worse than the disease.

[Harvy66]

@Hugovsky:

If I have to trade speed for security, I choose security every time. With Intel, it used to be a win-win but, with recent news… I just don't believe it so blindly anymore. Of course AMD is not the cure to all your problems but it sure starts to seem a little better.

A system with a speed of zero is perfectly secure, and perfectly useless.

[ivor]

PPP will still be somewhat slow after this gets patched. :)

[robi]

http://www.newsweek.com/apple-iphone-chip-vulnerability-most-disturbing-security-issue-decades-771638

[JKnott]

What's more is the Intel CEO sold $24M in stock months AFTER Google advised Intel of the problem, but before it was made public.

http://www.businessinsider.com/intel-ceo-krzanich-sold-shares-after-company-was-informed-of-chip-flaw-2018-1

[ivor]

https://www.netgate.com/blog/an-update-on-meltdown-and-spectre.html