Hey there.

So... you use an ad blocker. That's cool. Sometimes we do too.

But without ad revenue, we wouldn't even be here. And we might not be here much longer.

Please disable your ad blocker and click to continue.

Page 16 of 21 First ... 6151617 ... Last
  1. #151
    snoekie Guest
    It is all about breaking the chain of trust. You need to trick your PS3 to run your code at a sufficient low level. Just as the glitch hack on the XBOX, you can then manipulate the signature comparison (which is a memcmp) to always return true. Decrypting code was never a problem, because you need the public keys to do that (which are in the firmware). It's the private keys that made Firmwares up to 3.55 so interesting. By obtaining the private keys (which were obtainable by the fail of sony) we can make packages that run on OFW.

    Having 3.60 or 3.73 public keys won't help you, unless you have a CFW that will unsigned or mal-signed code. Obtaining the 3.60 public keys shouldn't be hard, since they are public.

    What I am missing in all of these discussions about keys is the mention whether they are public or private keys. This is a big difference.

  2. #152
    medi01 Guest
    Quote Originally Posted by snoekie
    Decrypting code was never a problem, because you need the public keys to do that (which are in the firmware).
    Orly? Go get PUBLIC lv0 keys pretty please.

    Quote Originally Posted by snoekie
    Having 3.60 or 3.73 public keys won't help you, unless you have a CFW that will unsigned or mal-signed code.
    BS. Did we need new firmware to run Uncharted 3? Nope. Guess what, JUST DECRYPTING EBOOT was enough. All we need are the keys to decrypt eboots. Since SDK didn't change, all games will still work. No need of custom FW at all.

    Quote Originally Posted by 404 View Post
    ...but trust me breakself is real....
    How do you know? Why didn't M... tell us the hash of the keys as undeniable proof, how does decrypting unknown file prove it?

  3. #153
    niwakun Guest
    Quote Originally Posted by iscnokia View Post
    I understand that PS3 console uses several levels of encryption and in order to unencrypt it
    Private key = sign things
    Public key = decrypt things

    seriously watch the fail0verflow vid again

    Quote Originally Posted by iscnokia View Post
    Also, that phony DOS windows showing that output is nothing that any program running what you want so I could also write a C program printing:

    printf ("I have a 3.60+ CFW \n");
    in dos its derived with "ECHO" by the way.

  4. #154
    CS67700 Guest
    If there's so much noise around it, it probably means they're private...

  5. #155
    elser1 Guest
    so many smart people on here but the keys are illusive still.. must be hard to get eh.. LOL

    surely someone here has what you all want.

  6. #156
    firebuddie Guest
    I find it surprising there's not more talk about the zero size self expolit load to HV found by Failoverflow and detailed in xx404xx doc links at start of this thread.

    If the HV could be exploited, it could be patched to NOT hide the lvl0 bootloder and therefore use HV to dump the bootloader, even if it is encrypted, it is a start.

    Like Maths and xx404xx keep hinting, it's all there on our PS3's. Just getting the sucker to give it up! Like I say, dont know why a known exploit of HV is not being discussed/followed up on, or maybe it is and I ain't on right IRC channels to hear about it?

  7. #157
    Join Date
    Apr 2005

    New PS3 Metldr2 Revision Dumped by DarkVolt as DumpMetldr.bin

    Following up on the previous PS3 Metldr news update and Guides, this weekend Spanish PlayStation 3 developer DarkVolt has made available dumpmetldr.bin via Elotrolado.net which appears to be a dump of the new PS3 Metldr revision found in PlayStation 3 CECH-2504 consoles (datecode 1b and above) followed by a PS3 Boot Loader SE Version 3.7.3 (lv0 segment) dump and more below.

    Download: PS3 Metldr2 DumpMetldr.bin / PS3 Boot Loader SE Version 3.7.3 (lv0 segment) / PS3 Metldr2 Dump (most complete head including) / UP0001-CMX000010_00-METDUMPER0000000.pkg / metldr_475-478_fixed.rar / metldr_475-478.7z by CMX via zecoxao / dumpers_421-478.zip by haxxxen

    To quote, roughly translated: Here I come to leave the metldr decryption: http://www.multiupload.com/YN4G8LJJK4 according fence can I go to publish a thing or two more.

    Seeks the root key of geohot within the metldr dump I published aver if it sounds the flute.. I am the source and the base is an exploit..

    Deneuve image but this time I am not clear. I have work I'll be realeasing more stuff. Saying this is not worthy... hehehe explanation:

    We Have a decrypted metldr here, if you see it you will see a little Is An elf Without the normal header. It contains the root keys That geohot publish and a couple of 0x30 addead from 3.50 and ahead, and it STILL USES IT.

    HAVING in the elf metldr we can put it the header and upload it in using it as anergistic unselfer for loaders! The metldr is still used in 3.74 (a debug already exists) and 3.73 retail too.

    The difference of charge IS that before the metldr used to take the files from CoreOS and now it deliverer LV0 via ram em to us and close the access to the file BUT WE CAN IT DECRYPTED with the keys from the root metldr added if we have the file.

    LV0 can be the decrypted if we fix the feat of math to support the bootldr and decrypts the metadata from the header from LV0 and decrypts this with the rest of the spaces with Their loaders.. Worthy is it not? hehe

    Edit to add, if you compare a ISOLDR from 3.55 with the metldr you will realize that they are almost the same, I mean the isoldr contains the updates for the metldr (virtual of course)

    That in and 3.60 + Also it IS inside of the LV0 so it every time can update the initial metldr boots with the new couple of the keys already have... uploading the metldr in anergistic http://pastie.org/private/2kijry6y7jwoiwsepqqcbq

    [Register or Login to view code]

    With Metldr have almost total control of the console as we see in the picture above, however also shows that the bootldr is the only part of the PS3 outside the Metldr, but (and I say this in complete ignorance but using a logic low) and you have full access to the console should be much simpler to access bootldr in any case if this is true it would mean a breakthrough.

    [Register or Login to view code]

    PS3 Boot Loader SE Version 3.7.3: http://pastebin.com/rk7eib9Y (lv0 segment) / http://pastebin.com/hJTFRp5P / http://pastebin.com/xkXxk8fM

    From by jon_17_: The loads metldr ldr, ldr but these must be authenticated before a hash that contains internally metldr himself. metldr2 comes in certain consoles not downgrade (dataCode 1b and higher) are the most modern consoles today.

    Metldr weighs 60KB (usually in some cases), the spu local store have 256KB. The loaders to load the LV0 be decrypted (always), lv1 (always) and lv2 (only in lpar_ps3). Decrypted the loaders themselves LV0, lv1 and lv2.

    The lv2 to be deciphered in the lpar_ps3 saved in the spu local_store isolated the idstorage, this stores the hash idstorage of valid executables.

    From zecoxao comes a Metldr LV2 Dumper for PS3 4.75 to 4.78 Retail Consoles by CMX, who states the following:

    Today is a special day. This marks an important release. You are now able to dump metldr from a simple pkg install, instead of using linux resources. That's right, thanks to CMX, this awesome bundle allows you to dump metldr without going through red ribbons and debians!

    Created by:

    Flatz, for the original root key dumper source.
    Joon and Mike, for the tests.

    CMX (he made it all possible)

    (The build script is ready to use, but i was too lazy to upload the modified pkg source in the first link )


    Finally, from haxxxen to quote: Since it is easy to port it in a few minutes, i have made now a pkg from erk/met dumper for fws 4.21, 4.46, 4.65, 4.70, 4.75, 4.76, 4.78 (cex or dex)

    Btw, you only need 5 symbols, so you can leave and remove the rest: toc, extend_kstack, copy_to_user, memset, memcpy. further it is only syscall table and those 2 gameos lpar thingies needed.

    On another note, you should remove/comment new_poke install, since it can mess up with cobra mode. disabled, the dumpers work fine regardless of running cobra or not.

    The lv1 patches can be done dynamically with search patterns and only htab and spe patch is needed, since the others are enabled by default (at least on rebug 4.21)

    More PlayStation 3 News...

  8. #158
    elser1 Guest
    i wish i knew what they are talking about.. LOL

  9. #159
    Foo Guest
    Here's what a good majority of the people don't know:

    Math told us how to do this already!!! There was a bit of a puzzle, but once you put it together you understand it. (If you understand this stuff)

    And DemonHades was right. It's possible through RAM.

  10. #160
    elser1 Guest
    its all over my head at this point in time.. if i wasn't so busy playing games i'd try to learn all this stuff.. LOL

Page 16 of 21 First ... 6151617 ... Last

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Log in