QUOTE(juggahax0r @ Jan 31 2011, 06:28 PM)

You can already get your CPU key on a dev just run the KK exploit easy. And for the record they didn't brick any kits , people are just stupid and don't know to take a dump of their system before they start messing around with shit, bricked would imply that their was no way to recover and their was. If you had a nand dump.
Considering that the person who released this is the same person who made the recovery that erased the NAND i don't see how anyone could trust him. And the only reason it was released was to make a point not to be nice and release software. Also the only people in here to get his back are his butt buddies.
And i do contribute thank you very much.
To be honest I didn't really have you in mind when I spoke about not contributing, but whatever anyways.
About the "already can get the cpu key" part, you could only do that on consoles that could run 4532/4548 to use the syscall handler exploits, that'd only be xenon boxes if I assume correctly (unless of course you port the jtag hack to a debug). This tool will allow you to dump the cpu key on any kits up to date including the slim revisions, that can somewhat be useful.
Also they may have released it to make a point, but they still did release it, which means they put the amount of work needed for this release to come. It was their work, thus releasing it was their call, if I work on something, no one should be telling me how/if I should release it, It's the same for everyone out there, as such I have the most profound disrespect regarding whoever leaked that tool in the first place.
Also I wonder how come no one's even thought of asking "how does it work ?" That's just me though.