QUOTE(grogger13 @ Feb 28 2007, 10:18 AM)

If one more person offers there infinite wisdom about things they know nothing about I'm not really gonna do anything, but it is really pissing me off. I came to the forum to find some explanation of what this hack can actually do and all I see are dumbasses saying, "now all we need to do is unblow the efuse" like there the first person to think of something like that.
Please would someone who actually knows something about this offer some insight. I know i dont know anything about it so I'm not gonna try.
Some people in this thread already made the right conclusion. This hack is interesting because it opens a whole new world of new hacking possibilities.
One of the key features in the xbox 360 security is the 'hypervisor'. Microsoft moved
all 'security sensitive' processes to the hypervisor this time. The hypervisor is in encrypted in RAM. Also, in the flash, where it is (most probably) stored, it is encrypted. In short, it's VERY VERY difficult to get to the decrypted hypervisor code.
With this hack, it finally becomes feasible to get that decrypted hypervisor code, containing all the security stuff, so that is the true merit of this hack, IMHO
So, now people will start to try to replicate this hack, which isn't as easy as it seems by the way. The main problem is: how to get the exploit code into the memory ? As you could also see in the video, they use the king kong demo. About a year ago, some people were using this this for shader experiments. Some people found a way to crash the x360. My idea is that they use a shader exploit to crash the x360 and then move the exploit code to the stack. Or maybe they use a shader exploit to just directly write to system RAM. But details on this are not public, so still, quite some research has to be done, even to just be able to replicate this hack ...
This post has been edited by TheSpecialist: Feb 28 2007, 12:49 PM