Intel (eat shit) admitted that Security Patch FUCKED UP BIG, CPUs not usable!

[Tony Tan]

http://fortune.com/2018/01/22/intel-corp-patching-faulty-chips/

Intel Says the Patch Designed to Fix Flawed Chips Is Faulty




The Intel logo is displayed outside of the Intel headquarters in Santa Clara, California on January 16, 2014.
Justin Sullivan—Getty Images
By Reuters
9:35 PM EST
Intel Corp (intc, +2.05%) said on Monday that patches it released to address two high-profile security vulnerabilities in its chips are faulty, advising customers, computer makers and cloud providers to stop installing them.

Intel Executive Vice President Navin Shenoy disclosed the problem in a statement on the chipmaker’s website, saying that patches released after months of development caused computers to reboot more often than normal and other “unpredictable” behavior.

“I apologize for any disruption this change in guidance may cause,” Shenoy said. “I assure you we are working around the clock to ensure we are addressing these issues.”

The issue of the faulty patches is separate from complaints by customers for weeks that the patches slow computer performance. Intel has said a typical home and business PC user should not see significant slowdowns.


Intel‘s failure to provide a usable patch could cause businesses to postpone purchasing new computers, said IDC analyst Mario Morales.

Intel is “still trying to get a handle on what’s really happening. They haven’t resolved the matter,” he said.

Intel asked technology providers to start testing a new version of the patches, which it began distributing on Saturday.

For more on the chip security flaw, watch Fortune’s video:

Apple Will Soon Have a Fix for Flawed Chips
“In the coming days.”

The warning came nearly three weeks after Intel confirmed on Jan. 3 that its chips were impacted by vulnerabilities known as Spectre and Meltdown, which make data on affected computers vulnerable to espionage.


Meltdown was specific to chips from Intel, as well as one from SoftBank Group’s ARM Holdings. Spectre affected nearly every modern computing device, including ones with chips fromIntel, ARM and Advanced Micro Devices.

Problems with the patches have been growing since Intel on Jan. 11 said they were causing higher reboot rates in its older chips and then last week that the problem was affecting newer processors.

The Wall Street Journal first reported Intel asking customers to halt using the patches.




https://www.theverge.com/2018/1/23/16922530/linus-torvalds-intel-spectre-cpu-fixes-comment

applied alongside a potential hit to performance.

“We take the feedback of industry partners seriously,” says an Intel spokesperson in a statement to The Register. “We are actively engaging with the Linux community, including Linus, as we seek to work together on solutions.”

Torvalds’ critical words about Intel come after weeks of the chip maker issuing carefully-worded statements in relation to performance impacts with its Spectre fixes. While Intel promised 90 percent of machines would have fixes available by now, it turns out that some of the patches have been making machines spontaneously reboot. Intel is now recommending that people hold off on updating firmware until the company has addressed the issues.

Intel says that it’s identified the issue behind the reboots on Broadwell and Haswell processors and is working towards releasing an update. Ivy Bridge, Sandy Bridge, Skylake, and Kaby Lake processors are also affected, and Intel says it’s “actively working on developing solutions” for those processors too. Microsoft was forced to halt its own patches for some AMD systems recently after some PCs were unbootable following the software updates. It’s clear the industry as a whole has been racing to fix Meltdown and Spectre, and the usual testing hasn’t been as vigorous as a result.




http://mashable.com/2018/01/22/intel-patch-spectre-meltdown-reboots/#N9BL_wZWAkq6
Intel tells some customers to avoid its official Spectre patch
Share on Facebook Share on Twitter

What's This?

Intel CEO Brian Krzanich has some thoughts.
Image: MANDEL NGAN /Getty Images
By Jack Morse13 hours ago

Remember Spectre and Meltdown?

The two recently disclosed vulnerabilities affecting all kinds of computer processors represented a huge threat to consumers and businesses around the globe. Thankfully, Intel offered up a partial fix — so all good, right?

Well, not exactly. You see, it turns out the patch that was issued by Intel has a few problems of its own. Now, things are so busted that the company is telling some of its customers to avoid the official patch altogether.

SEE ALSO: Intel CEO dives straight into Spectre, Meltdown at CES keynote

This unfortunate development came to light Monday, when Intel issued an official statement telling a groups of its customers to just slow their roll when it comes to updating their critically vulnerable systems.

"We recommend that OEMs, cloud service providers, system manufacturers, software vendors and end users stop deployment of current [patch] versions," reads the statement, "as they may introduce higher than expected reboots and other unpredictable system behavior."

So, it seems that after applying Intel firmware updates to systems running Intel Broadwell and Haswell CPUs, those same systems began suffering from unexpected reboots.

The company published a full list of Intel-based platforms that are impacted by this problem, and it's quite long.

While this definitely doesn't bode well for the company, Intel promises it's working on it.

"I apologize for any disruption this change in guidance may cause," notes Intel Executive Vice President Navin Shenoy. "The security of our products is critical for Intel, our customers and partners, and for me, personally. I assure you we are working around the clock to ensure we are addressing these issues."

And, hopefully, those left out in the cold by Intel should soon (Intel promises!) have a fix coming their way. Intel says it has "made good progress in developing a solution," so, assuming its forthcoming patch isn't also busted in some as-of-yet undetermined way, this mess may soon be in the rearview mirror.

Even so, it's not really a good look for the purported cure to cause additional ailments. But hey, maybe this stumble will distract people from the fact that Intel CEO Brian Krzanich sold $39 million in company stock and options after Intel learned about the vulnerability but before it was disclosed to the public. Maybe. But like the busted Intel patch rebooting customers' systems, it's probably best not to count on it.

WATCH: This robotic closet knows how to fold and sort your clothes

Topics: big-tech-companies, CPUs, hackers, hacking, Intel, meltdown, Spectre, Tech, vulnerabilities
You May LikePowered by ZergNet

What Was Found After Beats Headphones Were Taken ApartHuffingtonpost.com

Secrets Netflix Doesn't Want You to KnowGrunge.com

 

[Tony Tan]

This is TOO SERIOUS! People with SERVERS and CRITICAL APPLICATIONS will die. Credit Card and Bank Data Centers. Defense Security Network. Police. Medical system. Flight Control. Traffic Control. Missile Controls.... ALL FUCKED if REBOOT themselves. Planes will crash and missiles will hit Wrong Targets.



http://www.businessinsider.sg/intel...he-spectre-meltdown-attacks-2018-1/?r=US&IR=T

Intel is coming out with a new fix for Spectre and Meltdown, because the original caused unexpected reboots

Antonio Villas-Boas, Business Insider US
January 22, 2018
AddThis Sharing Buttons
Share to FacebookFacebookShare to TwitterTwitterShare to LinkedInLinkedInShare to EmailEmailShare to PrintPrint

Intel logo is seen behind LED lights in this illustration
Thomson Reuters

• Intel now says users should avoid installing and partners should stop distributing the patch it issued to protect against the Meltdown and Spectre attacks.
• The company had already acknowledged that the patch could lead to unexpected reboots, but had previously publicly advised users to install it anyway.
• The company has found the root cause of the problem – at least for some of its chips – and is working on a new patch.
• Intel is offering mixed messages – telling users to keep their computer systems up-to-date, but to avoid this fix.
• Consumers who have been trained to install any and all security updates may find it difficult to figure out how to avoid installing this particular patch.

When it comes to protecting computers from the Spectre and Meldown attacks, Intel issued some new advice Monday: customers and companies should avoid installing and its partners should stop distributing the fix it issued to address them.

Unfortunately for consumers, that may be easier said than done.

Intel previously acknowledged that the software patch it issued appeared to be causing some customers’ computers to reboot more frequently than normal. Intel said Monday it had identified the root cause of the reboot problem and is working on a new patch. In the meantime, the company said users shouldn’t install the old one.


“I apologize for any disruption this change in guidance may cause,” Navin Shenoy, executive vice president of Intel’s Data Center Group, said in a blog post. “The security of our products is critical for Intel, our customers and partners, and for me, personally. I assure you we are working around the clock to ensure we are addressing these issues.”

ADVERTISING
Intel’s announcement is likely to cause confusion for many consumers. At least for Windows users, patches such as the one Intel issued typically come through the Windows Update feature, not from Intel itself. It can be difficult to comb through those updates to weed out and avoid particular ones. And many consumers have been trained to just automatically install all security updates that come along.

Indeed, in virtually the next breath after telling users not to install this particular patch, Shenoy advised users to keep their computers updated – a decidedly mixed message at best.

“We continue to urge all customers to vigilantly maintain security best practice and for consumers to keep systems up-to-date,” he said.

The Spectre and Meldown attacks are made possible by an underlying vulnerability that affects nearly every computer chip and the vast majority of every PC, tablet and smartphone made over the last 20 years. The attacks, which became public earlier this month, could allow a malicious actor to exploit that vulnerability and get access to the secret data that’s on a computer, including passwords. Intel chips are particularly vulnerable to the Meltdown attack.



The rebooting problem was reported early on
Ever since Intel started issuing its patch for the vulnerability on January 3, some PC users have reported that their machines were rebooting more frequently that normal. The following week, Intel, in a blog post, acknowledged it was aware of the issues with the patch, noting that they seemed to particularly affect its fourth-generation Haswell and fifth-generation Broadwell chips, and said it was looking into the problem.

At the time, the company publicly advised users to continue to update their PCs with the fix. But quietly, the company told some users they should “delay” installing it, according to the Wall Street Journal.

Now the chip maker is giving that advice to everyone.

Intel has identified the root cause of the rebooting problem for Haswell and Broadwell chip models, Shenoy said. It’s testing a new patch with partners, he said.

There are still several Intel chip models that are reportedly experiencing rebooting issues, including its second-generation Sandy Bridge, third-generation Ivy Bridge, sixth-generation Skylake, and seventh-generation Kaby Lake models. A spokesperson for Intel told Business Insider that the company is working on the Haswell and Broadwell chips first, and will subsequently work on fixes for other models.

You can find a full list of Intel chips that are affected by the Spectre and Meltdown bugs here.

Unfortunately, there isn’t much those who are affected with the rebooting issues can do until Intel releases the new patch. Business Insider will report when the company announces it.

While you may not want to update your PC via the usual Windows Update feature quite yet, you should update individual software, apps, and programs, including your web browser.

• TAGS

 

[Tony Tan]

https://betanews.com/2018/01/23/intel-warning-stop-installing-meltdown-spectre-patches/

Intel tells customers to stop installing Meltdown/Spectre patches due to 'unpredictable' reboot issues

• By Mark Wycislik-Wilson
• Published 3 hours ago

5 Comments

• inShare1

The fallout from the Meltdown and Spectre bugs continues to plague Intel. The company has been hit with lawsuits, users complained about performance drops, and some users found that their computers were rendered unbootable. For people with Broadwell and Haswell chips, there was a problem with random reboots, and as a result of this -- some two weeks down the line -- Intel is now advising people to stop installing its patches.

Executive vice president Navin Shenoy says that the company is close to determining the root cause of the problem, apologized for reboots and "unpredictable system behaviour," and warns that customers should stop deploying the current version of the patches until an update is produced.

See also:

• Intel promises transparency as Meltdown patch causes reboot problems with Broadwell and Haswell chips
• Intel releases benchmark results detailing Meltdown patch performance slowdown
• Meltdown and Spectre: very few enterprise mobile devices are patched, and many will never be
• Intel: Meltdown and Spectre bugs also affect Ivy Bridge, Sandy Bridge, Skylake and Kaby Lake systems

Shenoy says that "we have now identified the root cause for Broadwell and Haswell platforms, and made good progress in developing a solution to address it," but this will come as little comfort to those who have been trying to secure their systems only to be left coping with instability instead.

The executive vice president insists that Intel is "working around the clock to ensure we are addressing these issues," but until a definite solution has been found and a suitable patch developed and tested, he has the following advice:

• We recommend that OEMs, cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions, as they may introduce higher than expected reboots and other unpredictable system behavior. For the full list of platforms, see the Intel.com Security Center site.
• We ask that our industry partners focus efforts on testing early versions of the updated solution so we can accelerate its release. We expect to share more details on timing later this week.
• We continue to urge all customers to vigilantly maintain security best practice and for consumers to keep systems up-to-date.

At the moment Intel is not giving any indication of just when the updated patches might be made available to everyone.

 

[Tony Tan]

https://thenextweb.com/insider/2018...ms-intel-for-crappy-meltdown-spectre-patches/


Linux creator slams Intel for crappy Meltdown/Spectre patches


by Abhimanyu Ghoshal — 7 hours ago in Insider

Credit: Kuttofos / YouTube

• 10
• 711
  shares
• 
  
• 
  
  
• 
  
• 
  
• 
  
• 
  
• 
  

Intel’s had a (mostly) crappy start to the year, thanks to the revelation of Meltdown and Spectre, two major security flaws affecting a wide range of its processors that are present in hundreds of thousands of devices around the world. It’s working to release fixes for them, but Linux creator Linus Torvalds is not impressed by the company’s efforts.

In a public email conversation between him and UK-based Amazon engineer David Woodhouse, Torvalds (pictured above giving the bird to Nvidia) calls the patches, “COMPLETE AND UTTER GARBAGE.”

According to him, the Meltdown patch requires the user to opt in and enable the fix while the computer boots up, when it really should just be enabled automatically. Torvalds believes that this isn’t being turned on by default because it could affect performance benchmark tests and make Intel look bad.

TechCrunch noted that he’s also mad about redundant fixes for previously mitigated security flaws, which he believes are being included to pad the patch, so it appears to solve a number of issues instead of merely addressing Meltdown.

In a statement released after the email exchange did the rounds, Intel said:

We take the feedback of industry partners seriously. We are actively engaging with the Linux community, including Linus, as we seek to work together on solutions.

It sounds like the company has a lot of work to do before it can declare the Meltdown fiasco done and over with – and that includes addressing Torvalds’ concerns.

After installing the official patches made available last week, users found that their computers were rebooting at random; Intel has now discovered what’s causing this issue; today, it’s urging users to skip those patches and await a better fix.

At CES 2018 earlier this month, Intel CEO Brian Krzanich promised that the company would patch all Meltdown/Spectre affected processors made in the past five years by the end of January. It’s already missed its deadline to sort out 95 percent of those processors by the end of the week during which CES took place.

This is one issue we can’t afford to hear more bad news about. Hopefully Intel will get its act together before it’s too late.

Read next: Wine 3.0 arrives on Android to let you run Windows apps on your phone

IntelTech

 

[Tony Tan]

https://www.lowyat.net/2018/153220/...tels-patches-spectre-meltdown-garbage-insane/

Linus Torvalds Calls Intel’s Patches For Spectre and Meltdown ‘Garbage And Insane’
John Law 1 hour ago 0 0 226 views

Oh Linus Torvalds, how we miss your unapologetic choice of words. From publicly swearing at NVIDIA for not providing enough support for Linux and Android back in 2012, to his OCD-induced and vulgarity-spewing tirade over lines of bad coding, the man is certainly a legend in the world of computing beyond his status as the father of Linux.

Recently, the man directed his ire towards Intel and its patches that are supposed to fix the Spectre and Meltdown flaws. Torvalds ire stems from the fact that Intel’s patches don’t actually fixing the problem outright but instead, offer what he describes as a protection flag as a feature to the existing problem.

“No, please. Do tell me your excuse. I would love to hear it.”
To put in a less-confusing way: Torvalds is saying that the Intel’s patches doesn’t treat the Spectre and Meltdown flaws as bugs. Instead, Intel is choosing to just leave the vulnerabilities in its chips as they are, and ship them out with the aforementioned protection patch as a feature.

Needless to say, Torvalds had some choice words for Intel, and in a message posted to the Linus kernel mailing list, he said that “as it is, the patches are complete and utter garbage,” and that “they do literally insane things.”

This isn’t Torvalds’ first time attacking Intel on the Spectre and Meltdown flaw. Earlier in the same month, he mouthed off by saying that “Intel needs to really take a long hard look at its CPUs, and actually admit that they have issues instead of writing PR blurbs that say everything works as designed.”

MORE: 2018 Will Be A Great Year To Buy A New Laptop
The Spectre and Meltdown vulnerabilities are flaws that are plaguing Intel’s processors, with Spectre being the nastier of the two. To be fair to Intel; the company is aware of the problem, and to date, Intel has released several patches to the flaws.

However, the semiconductor maker has since issued a statement on its site, advising users to hold out on installing the new security patch, at least until the company finds a better solution. All in all, it is likely that the threat of Spectre and Meltdown are going to be around for quite some time.

(Source: Hot Hardware, The Register, LKML.org, YouTube)

2

 

[Truth_Hurts]

To the Experts,

if that is the case, would it be better to get AMD? does AMD have such an issue?

 

[eatshitndie]

To the Experts,

if that is the case, would it be better to get AMD? does AMD have such an issue?

yes, but meltdown impacts intel and arm processors more than amd’s. spectre impacts intel, arm and amd processors. if you’re using a device with intel i5 and i7 cores, they are impacted by both with performance hits when you install patches. below chart shows unpatched core i7 running windows shit. good luck!

 

[kryonlight]

To the Experts,

if that is the case, would it be better to get AMD? does AMD have such an issue?

The current state of processor design is such that there is no guarantee of serious side effects due to cache issues caused by parallelism. I strongly feel that security issues shouldn't be handled by the processor and should be pushed further up into the operating system.

Program files shouldn't contain raw machine codes that can be just directly loaded and executed. Instead program files should only contain verifiable bytecodes that can be compiled into benign machine codes by the operating system. The benign machine codes can be cached inside an encrypted file that can only be decrypted and executed with a valid user password.

 

[Truth_Hurts]

yes, but meltdown impacts intel and arm processors more than amd’s. spectre impacts intel, arm and amd processors. if you’re using a device with intel i5 and i7 cores, they are impacted by both with performance hits when you install patches. below chart shows unpatched core i7 running windows shit. good luck!
View attachment 38256

Lucky I never buy new pc..will just stick with the existing one. The problem I have is my AMD laptop performs worse than my Intel i5. So I rather not upgrade because AMD performance is shit. N intel is not safe.

 

[eatshitndie]

Lucky I never buy new pc..will just stick with the existing one. The problem I have is my AMD laptop performs worse than my Intel i5. So I rather not upgrade because AMD performance is shit. N intel is not safe.

older intel chips are also impacted by both meltdown and spectre. the list below shows all intel chips that are impacted.

• Intel® Core™ i3 processor (45nm and 32nm)
• Intel® Core™ i5 processor (45nm and 32nm)
• Intel® Core™ i7 processor (45nm and 32nm)
• Intel® Core™ M processor family (45nm and 32nm)
• 2nd generation Intel® Core™ processors
• 3rd generation Intel® Core™ processors
• 4th generation Intel® Core™ processors
• 5th generation Intel® Core™ processors
• 6th generation Intel® Core™ processors
• 7th generation Intel® Core™ processors
• 8th generation Intel® Core™ processors
• Intel® Core™ X-series Processor Family for Intel® X99 platforms
• Intel® Core™ X-series Processor Family for Intel® X299 platforms
• Intel® Xeon® processor 3400 series
• Intel® Xeon® processor 3600 series
• Intel® Xeon® processor 5500 series
• Intel® Xeon® processor 5600 series
• Intel® Xeon® processor 6500 series
• Intel® Xeon® processor 7500 series
• Intel® Xeon® Processor E3 Family
• Intel® Xeon® Processor E3 v2 Family
• Intel® Xeon® Processor E3 v3 Family
• Intel® Xeon® Processor E3 v4 Family
• Intel® Xeon® Processor E3 v5 Family
• Intel® Xeon® Processor E3 v6 Family
• Intel® Xeon® Processor E5 Family
• Intel® Xeon® Processor E5 v2 Family
• Intel® Xeon® Processor E5 v3 Family
• Intel® Xeon® Processor E5 v4 Family
• Intel® Xeon® Processor E7 Family
• Intel® Xeon® Processor E7 v2 Family
• Intel® Xeon® Processor E7 v3 Family
• Intel® Xeon® Processor E7 v4 Family
• Intel® Xeon® Processor Scalable Family
• Intel® Xeon Phi™ Processor 3200, 5200, 7200 Series
• Intel® Atom™ Processor C Series
• Intel® Atom™ Processor E Series
• Intel® Atom™ Processor A Series
• Intel® Atom™ Processor x3 Series
• Intel® Atom™ Processor Z Series
• Intel® Celeron® Processor J Series
• Intel® Celeron® Processor N Series
• Intel® Pentium® Processor J Series
• Intel® Pentium® Processor N Series

 

[ejected.president]

Whoever the system admins who patched their servers with these are going to have their ass fucked by bosses. Fucking Intel, can not make secured CPU and can not even patch properly. Fuck Spider lah!

 

[eatshitndie]

Whoever the system admins who patched their servers with these are going to have their ass fucked by bosses. Fucking Intel, can not make secured CPU and can not even patch properly. Fuck Spider lah!

this is what you get when you hire too many indian chiefs to run amok. any company which hires "cheap" ah neh labor will get their comeuppance, oops i mean cum-uppance.

 

[Truth_Hurts]

this is what you get when you hire too many indian chiefs to run amok. any company which hires "cheap" ah neh labor will get their comeuppance, oops i mean cum-uppance.

But this is a long standing issue...the ah nehs have not been there that long. I hope intel implement a claw back clause n go after the culprits etc who created this mess

 

[eatshitndie]

But this is a long standing issue...the ah nehs have not been there that long. I hope intel implement a claw back clause n go after the culprits etc who created this mess

you can't be more wrong. the gm and leader of the p5 (pentium) group during its design and development phases was none other than vinod dham. the genesis of this fuck up began with the pentium chip.

https://en.wikipedia.org/wiki/Vinod_Dham

 

[Truth_Hurts]

you can't be more wrong. the gm and leader of the p5 (pentium) group during its design and development phases was none other than vinod dham. the genesis of this fuck up began with the pentium chip.

https://en.wikipedia.org/wiki/Vinod_Dham

Should claw back from him. Actually intel can take him to court for negligence or some term with regards to malicious intent. In Singkieland alot of employment contracts have a negligence cause etc. In ang mor lands also.

 

[eatshitndie]

Should claw back from him. Actually intel can take him to court for negligence or some term with regards to malicious intent. In Singkieland alot of employment contracts have a negligence cause etc. In ang mor lands also.

cannot liao lah. after so many years of selling hundreds of millions of chips if not billions and hefty profits, the case is in statutory limit territory. moreover, intel grows by leaps and bounds because of pentium's introduction to the pc market. it was then not a flaw but a much sought after feature to boost performance by storing raw un-encrypted data in kernel memory (using memory cache in the processor to make it an all in one chip) in order to speed up lookups of often-used info such as id, password, pin, personal data, name, dob, address, etc. that are used for access to other software and apps with need for log-in credentials. oem's, pc makers, buyers, and os software houses bought into it and were therefore willing partners and resellers. moreover, he's no longer with intel. he can't get fired from intel. intel and suppliers asked for that feature. he and his team delivered. the issue is only evident and relevant now because of apps requiring ever faster processing and lookups in trillions of instances per second, and hackers are more knowledgeable in exploiting the weaknesses of the firmware and kernel memory, not just os, apps, and other software.

 

[Truth_Hurts]

cannot liao lah. after so many years of selling hundreds of millions of chips if not billions and hefty profits, the case is in statutory limit territory. moreover, intel grows by leaps and bounds because of pentium's introduction to the pc market. it was then not a flaw but a much sought after feature to boost performance by storing raw un-encrypted data in kernel memory (using memory cache in the processor to make it an all in one chip) in order to speed up lookups of often-used info such as id, password, pin, personal data, name, dob, address, etc. that are used for access to other software and apps with need for log-in credentials. oem's, pc makers, buyers, and os software houses bought into it and were therefore willing partners and resellers. moreover, he's no longer with intel. he can't get fired from intel. intel and suppliers asked for that feature. he and his team delivered. the issue is only evident and relevant now because of apps requiring ever faster processing and lookups in trillions of instances per second, and hackers are more knowledgeable in exploiting the weaknesses of the firmware and kernel memory, not just os, apps, and other software.

yeah that is why USA companies are loosing out to ah tiong companies,,usa continues the way it does,,it is fucked...but I am using AMD now,,,and want to change back to intel,,,AMD is slow and runs hotter than intel,,,was about to get new equipment when this shit happen,,so if all got weakness,,,might as well just stick with the shit I got