Yesterday the whole alarm went off when it was revealed that the shooter had been able to obtain confidential information from AMD. Information including, depending on the hacker, information about the source code of the new AMD technology, which is closely related to RDNA 2 Technology and Navi GPU, Among you would be, the Xbox Series X GPU. At this point, many are making their own cabal about what this hacker actually has, but for now, AMD makes it clear that the hacker has indeed stolen.
Moderate wccftech Contacted AMD to obtain this information and disclose the response provided by AMD in this situation. Although what affects AMD right now is knowing that someone has been able to steal structured data from their servers, what seems most important is what the stolen code can say. Most of the movie cabal before I even knew what it was talking about, and in the end it didn't look that much. AMD specifies what the criminal left behind, where it clarifies what can and cannot be done by those who want to use that information.
What the thief had stolen:
-
Files are part of Verilog that is often used to build processors.
-
Verilog files mentioned represent one or more single functions on the GPU, NOT a full / real shot of the GPU. This is a very important conclusion and the context of intellectual property theft. This function is not particularly important, and is not part of AMD's IP core.
-
According to the hacker's screen, the unnamed files are not the same and are not even close to being a complete "source code". In other words, the total IP stolen represents the smallest fraction of the "source code" needed to build and design a GPU.
-
These Verilog files are built into a content schema that is only compatible with AMD's internal design language (in other words, this will be obsolete by a third).
And that's exactly what many have estimated since it was ripe, given the ridiculous amount requested as a ransom for not providing this information to third parties. AMD It sought what information it could take, and in addition to specifying what was taken, to convince everyone by confirming what it was It may or may not happen with that information that the hijacker was actually stolen.
-
It cannot be used to design or build any of the products mentioned, let alone.
-
Cannot be used to reverse engineer product performance.
-
Cannot be used to back up a developer for any product / detail feature. At least, with what has been shown that the hijacker has been stolen
-
The source estimates that the full range of files can be used to get to the highest possible specification, but this should not be a problem since most of this information is already public.
-
It does not contain any data that can be used more easily / faster than any security feature on AMD RDNA GPUs.
However, there are some dangers, especially if this information can be used to search for risks in other aspects of it. The fact is that at this time, investigating this opportunity may also be done to eliminate those risks. Details wouldn't see anything really important, in fact, AMD Theft, given that these types of situations are far more common and the information they would have gained is less important than the fact that he has made public the information that information has been stolen.
So it doesn't seem like the hints were suggested as to what that information could do and how it might affect, for example, the Xbox Series X. One of the biggest strengths that the hacker played was being able to provide information about those properties. that they could be sold to their competitors for a secret that they did not know would work in their technology. But it seems this approach, which is very important to it AMD, discarded.
