05-12-2010 #71Banned User
- Join Date
- Mar 2008
@TUHTA: what would be if we get forced the otheros to use other space then the one we wanna read out? is that possible through manipulation?
-rep from me too, please don't post useless information. If you've updated: FINE, if not: Great.
in another case - I get my 60GB ps3 tomorrow. It has a YLOD so on that fact I'll fix it, and (I don't know the fw version) get linux installed. I do have a small linux project I was working on a while back, involves a text-only shell and very light kernel.
I'm not sure if I can get it to lock the ethernet controller, but I'm definitely going to try anything I can. I have been out of this for too damn long and honestly - I'm tired of it. If there will be a time a CFW comes out, I'll be on that team to do it
I'll be going to school some time this year, not sure what exactly but programming will definitely be one of my courses. Regardless of what language or variant. Keep this thread updated [not with useless info], I have a friend willing to help me with his 10+ years of electronics knowledge lol
Let's see sony stop something that won't be on their network/radar or whatever you want to call it ;] If a CFW is released, I hope they don't expect us to be on their network using it. That would defeat the purpose and they could patch it with one of their updates in a split second without warning.
Peeps... Sorry for repeating myself but since nobody answered my question, I will ask again... As far as I know, the pups use asymmetric cryptography (meaning that sony puts a public key inside the ps3 and signs every pup with her private key - which never leaves HQ btw - that can only be decrypted using the public key inside the ps3).
How come now some people are claiming that the pup's only security is a sh1 hashing check and that they can replicate the process using a key and an algorithm retrieved from level 2?
Nothing makes sense to me... Can someone clear the whole matter up for me?
So, even with figuring out the SHA1 issue (and getting past it) - the best you can do is swap around some encrypted data for other encrypted data.
But i'm really pessimistic about the key ever get loaded to ram. (They can load it to isolated-SPU from the "bios".)
So I´m saying goodbye to GameOS homebrew for the time being...
Service Mode box, for instance having in-game xmb in 1.50, your typical hybrid debug-retail firmware, etc - its actually quite simple.
The problem becomes the HMAC-SHA1 issue, but find the proper way to recompute that (which, the program segment that checks the PUP's validity would have) - you can make your own PUP - so to say. Of course, you can only use encrypted contents, and it limits you greatly (the whole CoreOS thing).
is p2 emulation possible with this pup modification?? because other ps3 systems have ps2 support!
But be I'm wrong...