173w ago - A few days ago we saw the inside pics of PS JailBreak, and today SKFU (linked above) has posted that PSJailbreak is both detectable and bannable on PSN along with Mathieulh confirming confirming that GeoHot's exploit was used and that PS JailBreak can be easily dumped.
He went on to state: "Actually they used the geohot hack to get code with lv1 privileges running on the console, they then used this to 1. Dump lv1 2. dump the spm syscall table (that's after quite a bit of lv1 reversing to even figure the spm exists) 3. Use the actual spm syscalls to trick the spu into calculating the proper response for the dongle id of their choosing.
Without those steps that all require geohot's hack, they could never have gotten their dongle to successfully identify as a jig and they could never have triggered their hack.
The psjailbreak basically exploits the update manager which is the code that does the dongle auth located inside the spm itself inside lv1.
We don't have the payload it sends though because we don't have a dongle to sniff it from, thus we have yet to know what lv2 patches it does."
RichDevX has also tweeted (HERE, HERE, and HERE) the following: "Using the backup manager on PSN is like walking into a trap. Title: Backup Manager || Title ID: LAUN12345. FYI, dongle IDs can be revoked! Don't be surprised if error 0x8002A227 is returned."
This essentially means Sony may detect those launching the backup manager and sending the following response which suspends the console from PSN: SCE_NP_AUTH_ERROR_CONSOLE_ID_SUSPENDED
Currently PlayStation Network is down for maintenance, although unconfirmed if it is due to Sony implementing PS JailBreak detection.
To quote from SKFU: "While hackers usually had to work very hard to succeed in the videogame scene, now all seems to become a business of corruption and audacity.
A short timeline of the PSJailbreak. How it may have started, succeeded and may go on.
Part 1: Someone (called "the fake hacker" below) came in contact with an employee of a SONY service center. The fake hacker probably used a bit social engeneering until the employee agreed to sell him one of the SONY confidential JIG Sticks used in the service centers to test and repair broken PS3 SKU's.
Part 2: The fake hacker used documentation and software which was leaked by other SONY employees to study the JIG stick. The stick is used to boot a special firmware from itself before the original PS3 firmware starts. The now running system allows to execute debug/fake signed executables which can be created with SONY's official SDK.
Part 3: The fake hacker shared the information with his team members and people who were able to clone the stick. Probably in china as usual.
Part 4: The stick is clonable, so the fake hacker went on and used stolen/leaked software from SONY's official SDK to develope (the only real work he did!) the application known as "backup manager" which is used on the PS3 to dump and start the backups.
Part 5: The fake hacker distributes high illegal clones of the original JIG stick via several online shops including the "backup manager" which is also illegal as it's all created with stolen/leaked software and documentation by SONY.
Part 6: SONY may update the PS3's bootcode to prevent loading the stick. They also could log the "backup manager"'s game ID (LAUN-12345) when people go online. So they could identify who actually uses the illegal JIG clone and ban the affected consoles. This would be an illegal step aswell, but hey; it's SONY."
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Guys, you're stretching a bit too much with the USB disabling, etc. You have to think of whom we're dealing with here. Sony could do a number of things to protect themselves:
* Release newer, more secure JIGs to their service centers with different HW IDs and updated software. All older JIGs would be destroyed and their HW IDs and software invalidated. I'm more than certain that when they designed the PS3, they added the ability to recognize more than one HW ID for sending the PS3 into Service Mode, just for such an occasion as this.
* Add a "kill switch" of sorts to new PS3s during production to invalidate the older JIG ID, activate a similar killswitch in all older models via firmware.
* Ban all PS3s from PSN that contain either unsigned code, or log references to Jailbreak HW IDs and unauthorized apps. If I'm not mistaken, the only PS3s that can run unsigned code are Debug units, and they can't access PSN anyways (citation needed).
There's no need for them to cripple USB functions. I'm sure they have already gotten their hands on the original Jailbreak, and would have their R&D Department tearing it and all clones apart to invalidate them.
Should be doable to make sure those devices are recognized, and then only have the interfaces and access needed to run the associated software. Anything else should then not have access at all. And "the community" will rejoice, as piracy is "stopped".
If Sony is doing their usual thing, they'll do it. They haven't cared about the media hub part of the ps3 package since the beginning. Most likely it's going to serve as a good excuse to finally cap it once and for all, since external storage is, as we all know, evil. And encourages piracy, and watching unlicensed tv-shows you don't have access to unless you move to another country. This according to well-connected folks in the hierarchy. There's also the fact that "USB-sticks" are associated with "hacking". So you'd better believe some atechnical lalallala is planning something like this right now.
Of course - it won't actually fix the problem, and can be circumvented. But that's not how they work - the idea is to cull the perception (in particular circles) that the box is useful for anything but condoned Sony activities. I mean, these are the kinds of people who believe that a branded download store would be able to charge more for the same product as an unbranded one, and still get more sales. Then if that fails, they'll blame the team responsible for that particular project, and pull the finances.
Same thought-process happened with the linux-debacle most likely - they draw up a wishful thinking scenario that happens to involve customers who love doing exclusively the things that return money in the short term. Regardless of content, support for the products, the quality of the products, etc. And then dream up some fictional customer who will fit their decision. Then that fictional customer materialise in their focus-groups, thanks to creative question-asking. This then guides the interest for where to focus effort, until the customer base is so small the projects die out on their own. I've seen that first hand before, and I don't think they're.. in a hurry to change tack.