Soldato
Im just going to take my chances till Ryzen 2 comes out. CBA updating BIOS. I hate doing it.
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
I'm still a little confused as to what can be gained from the exploites, I thought passwords etc where encrypted?
According to the register https://www.theregister.co.uk/AMP/2018/01/05/spectre_flaws_explained/ only Skylake and newer will require a BIOS update to mitigate against Spectre 2. Older CPUs will rely on just the kernel countermeasures. Whether this is because they can't be bothered to fix older CPUs fully due to cost or time or they genuinely don't need it, I don't know.This could roll on for decades...
Intel PR, if it has not already will go into absolute overdrive putting out fires now, i expect the internet about to be flooded with benchmarks apparently showing no performance penalties, no real security flaws and general "everything is super at Intel, nothing to see here" articles going up in the next few days.
I just heard about this and unfortunately know very little about computer/network security (although probably a lot more than the average Joe.
I bought an i7 8700k in December for my gaming rig - will the software patch that would impact it's performance have already been installed? I noticed an 8% drop in BF1 fps recently, but I assumed this was as a result of a BF1 patch. I'd rather not install the patch, all I really care about with this rig is gaming performance. There's no data on there that I'd care about if it was accessed. Is it possible to avoid installing the performance hindering patch? (Or uninstall it if it has already been installed?)
Also, would having a secure VPN running constantly nullify the vurnerability or not?
All of my personal data is on my server which I will of course install all the fixes on.
Who really cares if the fixes slows performance though? I would much rather have Intel talk about how they are going to commit to making all their systems secure as advertised. Plus it's going to take years to see what effect the updates have on performance.
Interesting, I didn't know you could basically force Windows to side-load CPU microcode updates. I plan to try this tonight and see if the results from Get-SpeculationControlSettings change at all, that is assuming there are any microcode updates for Westmere-EP in the first place!Possibly doable yourself if I'm reading the below correctly?
http://forum.notebookreview.com/threads/how-to-update-microcode-from-windows.787152/
According to the register https://www.theregister.co.uk/AMP/2018/01/05/spectre_flaws_explained/ only Skylake and newer will require a BIOS update to mitigate against Spectre 2. Older CPUs will rely on just the kernel countermeasures. Whether this is because they can't be bothered to fix older CPUs fully due to cost or time or they genuinely don't need it, I don't know.
Well yeah, but you could offer me a chip 100x performance of anything on the market and I still wouldn't buy with these bugs. It's worthless.
It's not worthless. Because I would pay handsomely for a chip with "100x the performance of anything on the market" even if it had these bugs. One mans trash etc.Well yeah, but you could offer me a chip 100x performance of anything on the market and I still wouldn't buy with these bugs. It's worthless.
So my haswell doesnt? again. upgrading to AMD this year so meh.
It's not worthless. Because I would pay handsomely for a chip with "100x the performance of anything on the market" even if it had these bugs. One mans trash etc.
Yeah basically. I'd game on it and do everything else on another machine.And what you do with this chip? Run it in quarantine?
Surely any BIOS update is simply going to be a "workaround" to cope with a CPU vulnerability (on which the microcode can't be changed) and this will have a performance hit (perhaps minor) over and above the OS fix?...
Spectre variant 2: affects Intel and Arm cores. Pre-Skylake CPUs need a microcode update (so potentially a BIOS update) to help mitigate this.
...
They will if available - I misread when I posted earlier (have now corrected), pre-Skylake will just receive OS updates, Skylake and later should be getting/need a Microcode update.I have recently build a number of systems based on either the i7 7700 CPU (released Q1 2017) or the i5 7600K CPU (released Q1 2017); I take it that they should NOT need a BIOS update?
A workaround is all microcode updates are - hardware bugs exist in almost all CPUs ever made, microcode fixes them at a low software level.Surely any BIOS update is simply going to be a "workaround" to cope with a CPU vulnerability (on which the microcode can't be changed) and this will have a performance hit (perhaps minor) over and above the OS fix?
Will have little to no impact I would imagine. At the end of the day if you need a new PC, then you need a new PC - you aren't going to hold off indefinitely to see if this all blows over.As an aside - I wonder how Intel CPU sales are holding up at the minute?
As an aside - I wonder how Intel CPU sales are holding up at the minute?
Surely any BIOS update is simply going to be a "workaround" to cope with a CPU vulnerability (on which the microcode can't be changed) and this will have a performance hit (perhaps minor) over and above the OS fix?
.....
As an aside - I wonder how Intel CPU sales are holding up at the minute?
The conditional branch vulnerability can be mitigated if speculative execution can be halted on potentiallysensitive execution paths. On Intel x86 processors, “serializing instructions” appear to do this in practice, although their architecturally-guaranteed behavior is to “constrain speculative execution because the results of speculatively executed instructions are discarded”
This is different from ensuring that speculative execution will not occur or leak information. As a result, serialization instructions may not be an effective countermeasure on all processors or system configurations. In addition, of the three user-mode serializing instructions listed by Intel, only cpuid can be used in normal code, and it destroys many registers. The mfence and lfence (but not sfence) instructions also appear to work, with the added benefit that they do not destroy register contents ....