• Competitor rules

    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.

Dubious Research Discovers Ryzen vulnerabilites

Caporegime
Joined
17 Mar 2012
Posts
47,649
Location
ARC-L1, Stanton System
No CTS Labs are saying the problem is the same for any chipset that uses the one in questions be it Intel, AMD, Apple, Samsung or whomever. Intel just happens to be the only other option as the other person that it can relate too as there are only two parties utilising this chipset. So the statement of fact is from CTS Labs where we also took statements of facts about all the other research but want to throw away something because it doesn't fit the narrative being discussed.

It is counter intuitive to suggest you take CTS on their word for one element but not the other. That from what I can see was Humbugs point and that would correlate with common sense on the situation of what we are able to read.

Now in terms of CTS, they have not delved deeper with Intel although their statement suggests it would be a problem. However they are focusing on AMD. That then brings into question motive and other since they say on one side they know issues can be on all chipsets but don't back it up and instead seem to be purposefully causing issues.

The issue there is Rroff posts back as matter of fact statements that everyone is wrong without so much as even a statement from a "'professional company' (CTS-Labs are not professional in any way and all they have actually done more harm to security for users by the way they released the info). Instead Rroff has made an opinion and now utilising that as an argument to something he cannot prove and there is no evidence to support and telling everyone else they don't get it and are wrong. That is not a good basis to start a point of view and creating a debate because debating personal opinions is impossible by nature.

We don't know that Intel do have issues, we also don't know they don't. However if we believe the info CTS labs has produced and then take their statement of fact that the issue is on any machine with said chip. What then doubles down people even listening to Rroff is that anyone who happens to have the opinion that the issue is likely to be both Intel and AMD are now AMD fanboys and they are just pro-AMD and that is it does not help justify his point and just makes him sound childish without the ability to debate with common sense and neutrality.

It is for that reason I hadn't said much and not replied to Rroff for most part because there is nothing to actually debate and discuss like adults because nothing he has stated so far can be shown to any degree with facts and evidence. Making the whole thing a non starter.

Spot on, thanks Curly :)
 
Soldato
Joined
18 May 2010
Posts
22,376
Location
London
Thing is AMD have acknowledged these issues are present.

You need local access to the machine tho.

They have said they will patch it through bios and and work with ASmedia to patch the issue through their drivers.
 
Last edited:
Back
Top Bottom