QUOTE(Chan163 @ Feb 28 2007, 03:39 PM)

I don't think we will get that much from this kind of exploit anymore (at least the ones already on 4552), because M$ now knows what to look for. The next exploit has to be something else. I hope the 'final solution' will be more like a 'crack' instead of an exploit running only on certain systems...
Now about that resistor: Will the 360 run normally when this resistor is removed permanently? Will a new kernel be able to check if that efuse is blown?
I have a 4532 sitting right next to me and I'm thinking of removing the resistor before going online again. Does anyone have a picture where to find that thing (I don't want to search the whole board for it)?
Maybe but buffer overflows are not always easy to spot. That's why windows you see numerous attacks on the same MS application, IE or whatever, Often based around buffer overflow.
The coders are very good, they're not morons, it's just incredibly hard to prevent mistakes like buffer overflow. This is why Microsoft invented the .NET framework and languages like C#, So the programmer doesn't have to worry about memory allocations and so on... No matter how good a programmer you are, doing level C/ASM and even C++ you will make some mistakes in complex code.
So we might find another exploit like this. However, the problem is that Microsoft have this defence against that with eFuse. Whatever hack is developed, it has to fool the update that it doesn't need to blow the eFuse, or it has to find some way of preventing that counter-move from MS.