And now AMD will be investigated for "Possible Securities Fraud Violations"
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
for fux sake read the description and see the huge error they make trying akin "near-zero" risk with no risk. Do you work with them? They have the same ignorant ill concieved notion of the facts you attempt convey to obfuscate the train-wreck in security known with Intel as of late.And now AMD will be investigated for "Possible Securities Fraud Violations"
for fux sake read the description and see the huge error they make trying akin "near-zero" risk with no risk.
And in typical fashion you leave out context and apparent good sense. "Near-Zero" does not mean no fixes as you and the rest of the ignorant online masses in defense of Intel have propagated. Just because that is what you and the litigious few wish it to mean does not make it so. Even today AMD has still claimed a near zero risk on part #2. Even today the proper intelligent masses claim AMD has "no" impact from Meltdown, yet you still attempt to obfuscate that fact as to deter any ship jumpers from leaving the "ship on fire" afore known as Intel. You have not once commented "DIRECTLY" on the individual impacts of each part #1-3 or how they are in point of fact implemented ie: Physical access or remote (big difference here). You only comment that since there is a patch there must be a huge issue simply because you are ignorant of the REAL facts and further more wish to obfuscate the facts in service of Intel.We did spend a considerable time in this thread explaining the difference between initially claiming near-zero risk and hiding to general public the need of fixes and latter admitting that vulnerability of the CPUs and announcing the development of fixes: "We have defined additional steps through a combination of processor microcode updates and OS patches". <-- Underlined the relevant part.
And in typical fashion you leave out context and apparent good sense. "Near-Zero" does not mean no fixes as you and the rest of the ignorant online masses in defense of Intel have propagated.
Of course, "Near-Zero" doesn't mean "no fixes", but you keep ignoring that AMD engineers were developing those fixes, whereas the marketing dept hided them from public announcements.
Of course they could have gone the intel route, sat in silence then went full trump, talk and talk about nothing in general, related to the topic on hand. Just say it will be okay. Sometimes it is better to be proactive, something it seems intel are not being and again being ripped a new one by Linus. On the hardware side the problem seems manifestly worse for team blue, the gripe for team red is over language used in a technical sheet, I can see how you can make this out like team red is the bad one here.
Nothing wrong with your original source, just they didn't link to their source, which is why I linked to it myself.https://hardforum.com/threads/linus-torvalds-rips-into-intel.1953015/
This a better source for you then ?
BS as usual. Where is the proof of "hidden" fixes. They never mentioned any fixes in the initial report only impact of each variant. Then mentioned the roll out. Again this is you attempting to make a mountain out of a mole hill and inject more ignorance and vagueness as to adhere equal issue with AMD as with Intel, whereas Intel is far worse off.Of course, "Near-Zero" doesn't mean "no fixes", but you keep ignoring that AMD engineers were developing those fixes, whereas the marketing dept hided them from public announcements.
BS as usual. Where is the proof of "hidden" fixes.
They don't identify a need for additional steps, they simply make them available for anyone who requires maximum system security (I would say guaranteed security, but there is no guarantee in cyber security). Further is a keyword, but because it recognizes the existing mitigating features (a different architecture, according to amd).#103
Resume: Day 3 we know AMD is vulnerable and needs patches. Day 3 AMD makes first marketing statement and hides the need for fixes. Day 4 kernel developers already working in fixes in collaboration with AMD engineers. Day 11 AMD updates its public marketing statements and confirms the need for "additional steps through a combination of processor microcode updates and OS patches that we will make available to AMD customers and partners to further mitigate the threat". I underlined key words.
They don't identify a need for additional steps, they simply make them available for anyone who requires maximum system security (I would say guaranteed security, but there is no guarantee in cyber security). Further is a keyword, but because it recognizes the existing mitigating features (a different architecture, according to amd).
Again, there is no need. They did not disclose their existence, that much I don't dispute, but their stance is that they are not required for a safe and secure system that is protected from spectre to a degree that most people would be satisfied with. Even database users and DoD would probably be fine without the patches, but they were made because they simply do not want to take chances (for good reason).The exact wording of the update of the day 11 is "We have defined additional steps through a combination of processor microcode updates and OS patches", but those additional steps had been defined much before and AMD hided the need for those additional steps in the first public statements. The meaning of "further mitigate the threat" is obvious.
You are plain wrong.
The IBRS technique mentioned in the Fudzilla link that you gave us in your post #122 is a technique for Spectre not for Meltdown.
The IBRS, IBPB, and retpoline techniques discussed by Linus and David in the LKML thread I have given are techniques for Spectre.
their stance is that they are not required for a safe and secure system that is protected from spectre to a degree that most people would be satisfied with. Even database users and DoD would probably be fine without the patches, but they were made because they simply do not want to take chances (for good reason).
What are you stating? Those patches are enabled by default for AMD hardware on both Windows and linux.
That is a fishing expedition. Just another law firm looking for them easy bucks. Did you check out the form they wanted you to fill out if you owned AMD stock? It has nothing about stock worth or any questions other than you own stock currently. This type of behavior is not uncommon in the US law system and never seen as conclusive of anything more than the firm being ambulance chasers.Another new investigation for the same motives
https://www.prnewswire.com/news-rel...nc-and-zais-group-holdings-inc-300585629.html
I believe this makes the number five.
Sorry Kyle, won't happen again.
The patch for Meltdown is in the linux kernel, but it's not enabled by default for AMD.
That is a fishing expedition. Just another law firm looking for them easy bucks. Did you check out the form they wanted you to fill out if you owned AMD stock? It has nothing about stock worth or any questions other than you own stock currently. This type of behavior is not uncommon in the US law system and never seen as conclusive of anything more than the firm being ambulance chasers.
can you rewrite this, I have no clue what the hell you are saying.It is AMD's fault. If since the first minute AMD had communicated clearly that we know since the first minute --that AMD CPUs are vulnerable and need OS patches and microcode updates-- then nothing of this had happened.
can you rewrite this, I have no clue what the hell you are saying.
......
Keep on pretending and making things up if you want. The lawyers aren't going to waste their time on this if there are not grounds. There are two lawsuits.
juanrga Too many posts to pick from
Dismissed.
https://docs.justia.com/cases/federal/district-courts/california/candce/5:2018cv00321/321394/54