123w 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.
any fix for fuse 3.55?interested to see what the games like.thanks!...
Jar files found here /dev_flash/bdplayer/bdjstack/ in the same place as the java.security file.
it might of happened, i dont know. Just something that would seem a good way to at least scare people.
The fact they haven't though might be interesting?
I'm beginning to think there is none.
Anyway on looking around I found this /dev_flash/bdplayer/bdjstack/java.security, not that it was lost, but something at the bottom made me wonder.
:
# This is the system security properties file
# It should be named: ${java.home}/lib/security/java.security
# set the provider for security
security.provider.1=com.ibm.oti.security.provider.OTI
security.provider.2=com.ibm.j9.jce.provider.J9JCEProvider
security.provider.3=com.ibm.j9.jsse.J9JSSEProvider
# Default system policy class. This handles loading and managing
# the system security policy.
policy.provider=com.ibm.oti.util.DefaultPolicy
# First load the system policy file.
#policy.url.1=file:${java.home}/java.policy
# enables the expansion of special property tags inside policy files
# for example, ${java.home} will be expanded to the system property
# java.home
policy.expandProperties=true
# enables the use of command line policy file additions
# for example, -Djava.security.policy=file:/c:/mypolicy.policy
policy.allowSystemProperty=true
# Default keystore file format.
keystore.type=jks
# packages (or prefixes of) to checkPackageAccess...
# require RuntimePermission ("accessClassInPackage."+package)
package.access=com.ibm.oti.,com.sony.bdjstack.,com.sony.gemstack.,com.sony.mhpstack.
# packages (or prefixes of) to checkPackageDefinition ...
# require RuntimePermission ("defineClassInPackage."+package)
#
# no class loaders call checkPackageDefinition.
#
package.definition=com.aacsla.bluray.
:
Where it says "package.definition=com.aacsla.bluray" Does it mean it tells the Advanced Access Content System (AACS) Blu-ray Disc Pre-recorded Book, what Games and Bluerays we play as well as give use info on the disk thats in the drive. And this package.access=com.ibm.oti.,com.sony.bdjstack.,com.sony.gemstack.,com.sony.mhpstack? anyone know. Thanks