151w ago - There have been quite a few articles about possible things that Sony could end up doing to try and stop PS3 homebrew, and here are all the potential solutions I have noticed thus far.
PS3's will start sending a recently played list to check for homebrew titles / flagged names:
Pretty obvious solution here. Just start naming the homebrews after currently existing titles, Or titles of bad games. Such as we can take the game name / BLUS for the game FLOCK (worst game ever that nobody will play) and install a master manager under that name.
So while it looks like everyone is playing FLOCK, We will actually be using a multimanager for FTP's, Backups, and Emulators.
Sony disabling update by USB in the next patch:
There are a few options we can take if we end up accidentally getting hit with this.
For people who update and can no longer install from usb:
Either the firmware will need a pre-installed pkg manager with firmware update options, Or they will have to do a dnas redirect to their computer to check for an update.
For people who have not updated to the new firmware that disables it:
Download the firmware and simply patch the firmware to alter the USB access as well so it does not get disabled to begin with!
Sub-level secondary key-signing program:
Well. in this sense, We would be absolutely screwed. If we were to install the firmware, Even with a pkg signer, We wouldn't be able to do a thing.
We would simply have to hope that someone would notice it uses a secondary keysign, find it in the firmware, and remove it before it becomes a problem.
How to truly help everyone there is for future firmwares:
We need a program with a GUI for firmware patching, Yeah I know one is out already, But it needs more OPTIONS! Options people!!!
We need a windows / linux firmware patcher with a GUI featuring the following options in the form of checkboxes.
Level 1 patching
Level 2 patching
Level 3 patching
Install PKG File option
Update from USB option
Playstation store links in VIDEO tab
Playstation store links in GAME tab
Check for firmware update on network connection establish
I am certain a gui windows / linux auto-patcher for all current firmwares would be WONDERFUL and would probably make the world a happier place.
Hell, I don't know of a single person who wouldn't want these options for an autopatcher.
Oh, And someone hurry up and figure out the npdrm so we can get an autopatcher for EBOOT's that works.
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!
Hey, I would becareful of throwing to many ideas out there just because of the fact that Sony has been hitting the forums really hard. Just trying to get ideas on how they can fix their big "uh oh" and anything just to bust Geohot and FOF.
I know everyone is trying to collaborate out there but I feel some of these things like where some of the log files are kept, should be kept on the down low. I know us Devs are busy trying to make everyone happy, it will just take time.
I need to know one thing, Right at the begining of all the hackings, I was at OFW 3.41, an did the jailbreak, got online two times, but know i updated to OFW 3.55 (erased everything about the jailbreak (homebrew) before updating) am I safe of trouble of all this $ony crap ?
Yeah changing the ID of the Backup Managers and other apps is a great idea. People have been using that since the first jailbreak came out. Still to this day, all my updates of the Backup Manager get changed to a PSN game of my choice [I was the one who wrote the Ninja Backup Method a few months back, but enough chest beating]
My main concern is what the actual jailbreak device did once installed. The log files that get sent once boot up and even the logs that get sent when loading a PKG file can be changed and provided, but what scares me more so, is a log that tells Sony that a retail console is now a debug console (or was run with the jailbreak device)
The possible upcoming ban isn't a big issue. But then again it depends on everyone's situation. Myself, I have 3 xbox360s (2 modded) which leaves me one for online play. I understand that not everyone can own more than the one console, but if you play online alot, then that should be considered. I think the main problem we are going to face is the latest games requiring the latest firmware. Once Killzone 2 comes out, it might be impossible to play without updating the firmware. Unlike the Xbox360, it's easy to update the dash [though over the months, this too can be problematic when sneaky new ones to detect modified firmware] and still retain backup abilities. But with the new EBOOT.BIN requiring new firmwares, this is going to be more so.
Going to have a look at the creation of those new EBOOT [though note I'm not a programmer just yet, I'm really only good at writing long forums posts], and see if there is some way to get future firmware compatible games working.