Major Intel CPU vulnerability
-
The filing showed that the sales were part of a 10b5-1 plan, which was created on Oct. 30, just a month before Krzanich sold the shares. The 10b5-1 is a trading plan that company executives set up to sell stocks they own at a pre-determined time so that they are not accused of insider trading.
The reports about a 2015 plan appear to be misdirection to make people miss that there was a replacement plan put in place months after he know about the chip flaw. How much "proof" do you want? The "proof" that @StorageNinja isn't proof at all and relies solely on information like this not arising. That there was "a plan" before hand is a red herring.
-
One month before does not make an SEC pattern. This wasn't just not a pattern, it was basically a single transaction.
-
I really like the sources WordFence / Defiant uses:
-
-
-
Fedora and Spectre update: https://fedoramagazine.org/update-ongoing-meltdown-spectre-work/
-
Easily examine and understand any Windows system's hardware and software capability to
prevent Meltdown and Spectre attacks. -
@danp said in Major Intel CPU vulnerability:
Easily examine and understand any Windows system's hardware and software capability to
prevent Meltdown and Spectre attacks.Anyone tried this?
-
@ambarishrh said in Major Intel CPU vulnerability:
@danp said in Major Intel CPU vulnerability:
Easily examine and understand any Windows system's hardware and software capability to
prevent Meltdown and Spectre attacks.Anyone tried this?
Took a look at the laptop I was working on today with it. Found out it hadn't applied the latest updates, and it had the correct status and explanation both times I ran it.
Steve Gibson is a software guy, not a security specialist (obviously), he normally writes good programs/utilities.
-
@ambarishrh said in Major Intel CPU vulnerability:
@danp said in Major Intel CPU vulnerability:
Easily examine and understand any Windows system's hardware and software capability to
prevent Meltdown and Spectre attacks.Anyone tried this?
Yep. I have on a Dell R230 and R620. It correctly identified that the R230 was fully updated and as patched as possible, and that the R620 was still waiting for the microcode and bios update from Dell. Nice and easy for validation once you've applied your patches and updates.
-
Alot of really good content in this thread. I am thinking I should rename it to reflect updates on Spectre/Meltdown. Any ideas on renaming it?
-
@irj said in Major Intel CPU vulnerability:
Alot of really good content in this thread. I am thinking I should rename it to reflect updates on Spectre/Meltdown. Any ideas on renaming it?
Spectre & Meltdown
-
Ami correct, Intel isnt even going to release patch for the vast majority of the cpus they sold in the last 10 years? That is what i care about, the 'ancient' 2013 cpus i have in my server room that wont be getting patched. Not to mention the 4930k i have at home that is still faster than most of what they sell today, but wont be patched either.
-
@momurda said in Major Intel CPU vulnerability:
Ami correct, Intel isnt even going to release patch for the vast majority of the cpus they sold in the last 10 years? That is what i care about, the 'ancient' 2013 cpus i have in my server room that wont be getting patched. Not to mention the 4930k i have at home that is still faster than most of what they sell today, but wont be patched either.
I wouldn't hold my breath, this vulnerability has bolstered their future sales for any diehard Intel fans.
-
@momurda said in Major Intel CPU vulnerability:
Not to mention the 4930k i have at home that is still faster than most of what they sell today, but wont be patched either.
Well yeah... a $1,000 CPU you bought years ago would of course be better than a <$200 CPU you buy today.
If you spend $1000 on a CPU today, it'll be WAY better than your 4930k.
It doesn't make sense to patch CPUs based on their performance level...
-
@tim_g It was 500 dollars. Bought in 2013. Still not getting a fix, that is the problem. Dont give a fuck how fast it is. Same with the Xeons in the server room.
This is the largest chipmaker in the world, they wont even make out a fix for over 2/3 of their customers. This would be like GM having antilock brake problems for 15 years on all cars, and only giving recalls out to cars sold in the last 3 years. total bullshit. -
@momurda said in Major Intel CPU vulnerability:
@tim_g It was 500 dollars. Bought in 2013. Still not getting a fix, that is the problem. Dont give a fuck how fast it is. Same with the Xeons in the server room.
This is the largest chipmaker in the world, they wont even make out a fix for over 2/3 of their customers. This would be like GM having antilock brake problems for 15 years on all cars, and only giving recalls out to cars sold in the last 3 years. total bullshit.The car analogy sold me. With this type of vulnerability the safety is very similar to having a brake problem.
-
@momurda said in Major Intel CPU vulnerability:
@tim_g It was 500 dollars. Bought in 2013. Still not getting a fix, that is the problem. Dont give a fuck how fast it is. Same with the Xeons in the server room.
This is the largest chipmaker in the world, they wont even make out a fix for over 2/3 of their customers. This would be like GM having antilock brake problems for 15 years on all cars, and only giving recalls out to cars sold in the last 3 years. total bullshit.There are federal mandates on how long automakers must make recalls.
I don't think such a thing exists for things like this. Should their be? Oh hell yeah! But frankly I don't expect it to be more than 5 years (though 10 would be great).
It would be awesome to see federal law - if you make a computer based/software based widget, you must provide security related fixes for 10 years.
LOL - like that will ever happen.
-
@momurda said in Major Intel CPU vulnerability:
@tim_g It was 500 dollars. Bought in 2013. Still not getting a fix, that is the problem. Dont give a fuck how fast it is. Same with the Xeons in the server room.
This is the largest chipmaker in the world, they wont even make out a fix for over 2/3 of their customers. This would be like GM having antilock brake problems for 15 years on all cars, and only giving recalls out to cars sold in the last 3 years. total bullshit.Yeah I get the point. I agree they should provide a fix for them all as far back as Operating System vendors (Microsoft, Apple, Linux Distros, etc) will provide OS patches for AT LEAST.
-
@dashrender said in Major Intel CPU vulnerability:
@momurda said in Major Intel CPU vulnerability:
@tim_g It was 500 dollars. Bought in 2013. Still not getting a fix, that is the problem. Dont give a fuck how fast it is. Same with the Xeons in the server room.
This is the largest chipmaker in the world, they wont even make out a fix for over 2/3 of their customers. This would be like GM having antilock brake problems for 15 years on all cars, and only giving recalls out to cars sold in the last 3 years. total bullshit.There are federal mandates on how long automakers must make recalls.
I don't think such a thing exists for things like this. Should their be? Oh hell yeah! But frankly I don't expect it to be more than 5 years (though 10 would be great).
It would be awesome to see federal law - if you make a computer based/software based widget, you must provide security related fixes for 10 years.
LOL - like that will ever happen.
I don't think that it would be great. It would encourage all kinds of bad things, like intentionally fly by night organizations and a lot of small, cheap stuff not able to be made.
