• IP addresses are NOT logged in this forum so there's no point asking. Please note that this forum is full of homophobes, racists, lunatics, schizophrenics & absolute nut jobs with a smattering of geniuses, Chinese chauvinists, Moderate Muslims and last but not least a couple of "know-it-alls" constantly sprouting their dubious wisdom. If you believe that content generated by unsavory characters might cause you offense PLEASE LEAVE NOW! Sammyboy Admin and Staff are not responsible for your hurt feelings should you choose to read any of the content here.

    The OTHER forum is HERE so please stop asking.

Sam pse initiate Class Action in SG63 sue Intel's Pants Off and split $$$

motormafia

Alfrescian
Loyal
https://arstechnica.com/gadgets/201...tion-lawsuits-regarding-meltdown-and-spectre/

Intel faces class action lawsuits regarding Meltdown and Spectre
Class action lawsuits have been filed in California, Indiana, and Oregon.
Samuel Axon - 1/6/2018, 8:20 AM

intel-core-i7-800x534.jpg

Enlarge / An Intel CPU.
Mark Walton
133

Three class action complaints have been filed against Intel over the Meltdown and Spectre CPU security flaws that were discovered by researchers earlier this year and widely publicized earlier this week.

What’s behind the Intel design flaw forcing numerous patches?
The three lawsuits—filed in California, Indiana, and Oregon (PDF)—cite not just the security vulnerabilities and their potential impact, but also Intel's response time to them. Researchers notified Intel about the flaws in June. Now, Intel faces a big headache. The vast majority of its CPUs in use today are impacted, and more class action complaints may be filed beyond these three.

The three complaints also cite suggestions that devices using Intel's CPUs will see significant slowdown as a result of addressing the security flaws. However, that point is in some dispute. In the course of its various public efforts to mitigate damage and address concerns, Intel has publicly said in a statement that these concerns are overblown:

Intel has begun providing software and firmware updates to mitigate these exploits. Contrary to some reports, any performance impacts are workload-dependent, and, for the average computer user, should not be significant and will be mitigated over time.

Google, whose Project Zero team was involved in the initial discovery of the vulnerabilities, seemed to support Intel's claim when it wrote in its security blog about performance on its devices:

There has been speculation that the deployment of KPTI causes significant performance slowdowns. Performance can vary, as the impact of the KPTI mitigations depends on the rate of system calls made by an application. On most of our workloads, including our cloud infrastructure, we see negligible impact on performance. In our own testing, we have found that microbenchmarks can show an exaggerated impact. Of course, Google recommends thorough testing in your environment before deployment; we cannot guarantee any particular performance or operational impact.

Either way, the costs for Intel after Meltdown and Spectre could be significant. The Guardian consulted sources such as Fort Pitt Capital Group analyst Kim Forrest to paint a picture of what Intel faces. Regardless of the outcome of these class action suits, the paper writes that Intel will likely find itself in a poor bargaining position with its cloud customers and other enterprise partners and that it will likely have to spend more heavily on security in the future.

Samuel Axon Based in Los Angeles, Samuel is the Senior Reviews Editor at Ars Technica, where he covers Apple products, display technology, internal PC hardware, and more. He is a reformed media executive who has been writing about technology for 10 years at Ars Technica, Engadget, Mashable, PC World, and many others.
 

motormafia

Alfrescian
Loyal
https://www.theguardian.com/technol...ction-lawsuits-meltdown-spectre-bugs-computer

Intel facing class-action lawsuits over Meltdown and Spectre bugs
Plaintiffs claim compensation for security flaws and alleged slowdown that fixing computers will cause, while corporations count cost of corrections



‘The potential liability is big for Intel,’ said Eric Johnson of Vanderbilt University’s Owen Graduate School of Management. ‘Everybody will be scrambling over the next few days to figure out just how big it is.’ Photograph: Dado Ruvic/Reuters
Samuel Gibbs

Fri 5 Jan ‘18 13.52 GMT Last modified on Fri 5 Jan ‘18 22.00 GMT


Shares
261

Intel has been hit with at least three class-action lawsuits over the major processor vulnerabilities revealed this week.

The flaws, called Meltdown and Spectre, exist within virtually all modern processors and could allow hackers to steal sensitive data although no data breaches have been reported yet. While Spectre affects processors made by a variety of firms, Meltdown appears to primarily affect Intel processors made since 1995.

Three separate class-action lawsuits have been filed by plaintiffs in California, Oregon and Indiana seeking compensation, with more expected. All three cite the security vulnerability and Intel’s delay in public disclosure from when it was first notified by researchers of the flaws in June. Intel said in a statement it “can confirm it is aware of the class actions but as these proceedings are ongoing, it would be inappropriate to comment”.

The plaintiffs also cite the alleged computer slowdown that will be caused by the fixes needed to address the security concerns, which Intel disputes is a major factor. “Contrary to some reports, any performance impacts are workload-dependent, and, for the average computer user, should not be significant and will be mitigated over time,” Intel said in an earlier statement.

Q&A
What can I do about the Meltdown and Spectre flaws?
“The security vulnerability revealed by these reports suggests that this may be one of the largest security flaws ever facing the American public,” said Bill Doyle of Doyle APC, one of the lawyers representing plaintiffs Steven Garcia and Anthony Stachowiak who filed suit in the northern district of California. “It is imperative that Intel act swiftly to fix the problem and ensure consumers are fully compensated for all losses suffered as a result of their actions.”

Advertisement
Chris Cantrell of Doyle APC, told Law.com: “I fully expect there to be additional filings [on behalf of consumers and businesses] and that this will go the usual route of multidistrict litigation. Just the sheer number of devices that we’re talking about … most of the desktop and laptop computers in use today.”

Legal experts said consumers would have to prove concrete damages and harm to proceed with claims. But experts also expect that consumer class-action lawsuits may be just one cost Intel will face in the wake of the Meltdown revelations.

Eric Johnson, dean of Vanderbilt University’s Owen Graduate School of Management, said: “The potential liability is big for Intel. Everybody will be scrambling over the next few days to figure out just how big it is.”

Big cloud service providers such as Amazon, Google and Microsoft will likely seek some form of compensation from Intel for any software or hardware fixes they are forced to make and that could potentially impact their overall computational capacity, security experts said.

Amazon, Microsoft and Google all said they do not expect significant performance problems for most of their cloud computing customers.

But the incident is likely to spur cloud companies to press Intel for lower prices on chips in future talks, said Kim Forrest, senior equity research analyst at Fort Pitt Capital Group in Pittsburgh, which owns shares in Intel.

“What [Intel’s cloud customers] are going to say is, ‘you wronged us, we hate you, but if we can get a discount, we’ll still buy from you’,” Forrest said.

Forrest also suggests Intel may have to increase its chip development spending to focus on security.

Banks and financial services firms are trying to understand what it will cost to respond to the security issues, the Financial Services Information Sharing and Analysis Center (FS-ISAC) said in a statement.

The global industry group added: “In addition to the security considerations raised by this design flaw, performance degradation is expected, which could require more processing power for affected systems to compensate and maintain current baseline performance.

“There will need to be consideration and balance between fixing the potential security threat v the performance and other possible impact to systems.”

Since you’re here …
… we have a small favour to ask. More people are reading the Guardian than ever but advertising revenues across the media are falling fast. And unlike many news organisations, we haven’t put up a paywall – we want to keep our journalism as open as we can. So you can see why we need to ask for your help. The Guardian’s independent, investigative journalism takes a lot of time, money and hard work to produce. But we do it because we believe our perspective matters – because it might well be your perspective, too.

I’ve been enjoying the Guardian’s top-quality journalism for several years now. Today, when so much seems to be going wrong in the world, the Guardian is working hard to confront and challenge those in power. I want to support that. Robb H, Canada
If everyone who reads our reporting, who likes it, helps fund it, our future would be much more secure. For as little as £1, you can support the Guardian – and it only takes a minute. Thank you.

Become a supporter
Make a contribution
paypal-and-credit-card.png
 

eatshitndie

Alfrescian (Inf)
Asset
it's not a bug. it's a design feature called "speculative execution". to speed up execution and make the firmware more efficient, the kernel speculates on a set of instructions that happen frequently and preemptively executes those. but when they don't happen, these instructions are suspended and memory in kernel unwound but left intact in real-time storage. since memory in the kernel is not encrypted, erased nor flushed, it can be exploited. meltdown can be mitigated with a software update, but not spectre. spectre exploits the hardware design flaw in the microprocessor and may force a total redesign.
 
Top