[freestylemaster]

Originally Posted by lunuxx indeed somewhat out of place to mention, but its the truth i cant do very much on the tv sometimes and id rather not bore everyone in the room by having the tv sit on a black screen fyi about the hex2key i fixed one and left a note on the wiki so there are 2 links to hex2key the edit is the one i slightly repaired all credit for the app goes to anon for creating it its supposed to make a binary file

I used the edited one. So is it only to convert hex to ANSI ? after creation of the bin file and opening it with notepad gives me the exact ANSI code.

[baargle]

Can anyone explain what this actually brings? If not for the end user, then the developer. What is now more open that wasn't before. If the flow chart a nice member posted a couple of pages back is to be believed, then nothing?

Slightly confused, as this was talked about as the jewel of PS3 hacking, Not by ignorant people who can't hack like myself, but in news articles on here, psx-scene. (Arguable over if they are any less ignorant than myself but not the point)

So this is nothing then?

[8E068EDFA0C8DEA3]

Originally Posted by Warning His ps3 is hooked up to his tv, so he uses his computer to access his ps3. I do not see anything strange about that. Someday when you have a significant other you will understand the need to compromise tv usage.

I have 3 26'' TVs, one for each bedroom, they are cheap nowadays. I already understand relationship stuff but wouldn't try to prove by talking about it in a ps3 hacking tutorial.

Originally Posted by lunuxx indeed somewhat out of place to mention, but its the truth i cant do very much on the tv sometimes and id rather not bore everyone in the room by having the tv sit on a black screen fyi about the hex2key i fixed one and left a note on the wiki so there are 2 links to hex2key the edit is the one i slightly repaired all credit for the app goes to anon for creating it its supposed to make a binary file

yeah man I understand, it was just me drunk posting. thanks for your hard work and contribution.

[lunuxx]

Originally Posted by 8E068EDFA0C8DEA3 I have 3 26'' TVs, one for each bedroom, they are cheap nowadays. I already understand relationship stuff but wouldn't try to prove by talking about it in a ps3 hacking tutorial. yeah man I understand, it was just me drunk posting. thanks for your hard work and contribution.

i dont think i need to explain myself, though i already have go ahead and think what your gonna think and what not, instead of trying to insult me why dont you try to find out more if your that damn interested in my personal life. follow me on twitter or other social sites whatever. because i dont own another television and/or i dont feel like being apart from my family shut up in another room of the house for hours is really none of your business but there i just explained more. (which i shouldnt have to do)

[VIRGIN KLM]

Questions (please don't laugh if I sound funny):

1. To what I understand, this could lead to having kernel access to PS3 right?
Since ps2 emu self rely on kernel wouldn't we be able to do exactly what Cobra did in a more ''native way''? Also wouldn't this actually tackle with a hack the checks PS3 does on PS3/PSOne games if the disc you insert is an original disc or a backup?

2. Also since metldr is the head of the whole chain of trust procedure, wouldn't we be able to make modified firmwares with stuff like modified (and funtional) vsh.self and pre-vsh stuff like the PSP plugin loader, without breaking the chain of trust of PS3?

3. Aren't we now able to enable the 8th SPU of PS3 and use it on GameOS?(Don't tell me that it's too dangerous and that by default Sony had dissabled it to tackle production failures, it's not an answer to my question and I already know that)

[Master_Teeee]

Okay guys, just registered to post this...

Metldr (meta loader) is one of the lowest level functions of the P$3. It is a per console, unique, hardware based code... Meaning the one for your console, is only for your console. Each one has its own. I will refer to this as your 'hard key'.

Now, if you remember, back before geohot got sued, he released a set of keys, most important of which (for all your pirates out there), was the appldr (application loader) key. These are public keys, meaning that every P$3 made uses the SAME keys... This is how your P$3 decides whether the .pup (a firmware file [3.55 for example]) is genuine, or fake. These keys are decided by software, and therefore don't physically exist. This means that they can be updated whenever $ony see's fit, and is the reason modern games won't run on old firmwares.

Now, if you also cast your mind back, you'll remember that when geohot was about to get sued, he posted a comment similar to, "So no one STILL knows how I got the metldr keys???? ". He mentioned this, because if the metldr encryption key is known, then the soft keys can be decrypted. If the soft keys can be decrypted you can exploit the appldr, and have all your backup managers etc, on any firmware.

What makes this metldr key so special, is that, unlike the 'soft' keys, no update can be brought out to modify your metldr key. And, so long as you always know your metldr key (which you can do now), you will ALWAYS know your 'soft' keys, which are what 99% of you are here to try and find out.

Put simply:
metldr key = soft keys = cfw

This is why it's taken so long to get past 3.55. Geohot released the 'soft' keys, using his own metldr exploit (one would imagine was very similar, if not identical to this piece of C), but never released the method with which to obtain the metldr key itself. So the soft keys released could be updated, and, as we all know they were, and the system re-secured... Now however, we have full access to decrypt the soft keys, effectively continuing where geohot left off.

I hope that this makes sense to at least a couple of you, and sheds some light as to what this means for the scene, and also why people like math and geo were so reluctant to release these exploits.

Peace...

[mosstopher]

Originally Posted by Master_Teeee Okay guys, just registered to post this... (---edited for space---) ...Peace...

Great post, Nice, simple explanations for people like me who, whilst having unending interest and enthusiasm, lack the skills and the brainpower to understand anything!

[gregory2590]

Originally Posted by Master_Teeee Okay guys, just registered to post this... Metldr (meta loader) is one of the lowest level functions of the P$3. It is a per console, unique, hardware based code... Meaning the one for your console, is only for your console. Each one has its own. I will refer to this as your 'hard key'. Now, if you remember, back before geohot got sued, he released a set of keys, most important of which (for all your pirates out there), was the appldr (application loader) key. These are public keys, meaning that every P$3 made uses the SAME keys... This is how your P$3 decides whether the .pup (a firmware file [3.55 for example]) is genuine, or fake. These keys are decided by software, and therefore don't physically exist. This means that they can be updated whenever $ony see's fit, and is the reason modern games won't run on old firmwares. Now, if you also cast your mind back, you'll remember that when geohot was about to get sued, he posted a comment similar to, "So no one STILL knows how I got the metldr keys???? ". He mentioned this, because if the metldr encryption key is known, then the soft keys can be decrypted. If the soft keys can be decrypted you can exploit the appldr, and have all your backup managers etc, on any firmware. What makes this metldr key so special, is that, unlike the 'soft' keys, no update can be brought out to modify your metldr key. And, so long as you always know your metldr key (which you can do now), you will ALWAYS know your 'soft' keys, which are what 99% of you are here to try and find out. Put simply: metldr key = soft keys = cfw This is why it's taken so long to get past 3.55. Geohot released the 'soft' keys, using his own metldr exploit (one would imagine was very similar, if not identical to this piece of C), but never released the method with which to obtain the metldr key itself. So the soft keys released could be updated, and, as we all know they were, and the system re-secured... Now however, we have full access to decrypt the soft keys, effectively continuing where geohot left off. I hope that this makes sense to at least a couple of you, and sheds some light as to what this means for the scene, and also why people like math and geo were so reluctant to release these exploits. Peace...

HOLY ****

I WAS WAITING FOR "THAT ONE POST" WHERE SOMEONE MAKES SENSE ON EXPLAINING WHAT THIS MEANS!

+9001 internets to you. Lurk here more please.

[Viriatus]

Originally Posted by muny21 this thread needs to be locked but i guess the mods and/or admins here love drama and have nothing else to do but read through pages and pages of bickering. lock this thread and only update as needed.

I gotta disagree with you.

There's quite a bit of usefull information beeing shared around here, you just gotta look past the whole mathieu flames.


BTW, thanks master_teee been searching the whole thread for some information of what could be expected from the metldr leak.

[luqi]

Originally Posted by Master_Teeee Okay guys, just registered to post this... Metldr (meta loader) is one of the lowest level functions of the P$3. It is a per console, unique, hardware based code... Meaning the one for your console, is only for your console. Each one has its own. I will refer to this as your 'hard key'. Now, if you remember, back before geohot got sued, he released a set of keys, most important of which (for all your pirates out there), was the appldr (application loader) key. These are public keys, meaning that every P$3 made uses the SAME keys... This is how your P$3 decides whether the .pup (a firmware file [3.55 for example]) is genuine, or fake. These keys are decided by software, and therefore don't physically exist. This means that they can be updated whenever $ony see's fit, and is the reason modern games won't run on old firmwares. Now, if you also cast your mind back, you'll remember that when geohot was about to get sued, he posted a comment similar to, "So no one STILL knows how I got the metldr keys???? ". He mentioned this, because if the metldr encryption key is known, then the soft keys can be decrypted. If the soft keys can be decrypted you can exploit the appldr, and have all your backup managers etc, on any firmware. What makes this metldr key so special, is that, unlike the 'soft' keys, no update can be brought out to modify your metldr key. And, so long as you always know your metldr key (which you can do now), you will ALWAYS know your 'soft' keys, which are what 99% of you are here to try and find out. Put simply: metldr key = soft keys = cfw This is why it's taken so long to get past 3.55. Geohot released the 'soft' keys, using his own metldr exploit (one would imagine was very similar, if not identical to this piece of C), but never released the method with which to obtain the metldr key itself. So the soft keys released could be updated, and, as we all know they were, and the system re-secured... Now however, we have full access to decrypt the soft keys, effectively continuing where geohot left off. I hope that this makes sense to at least a couple of you, and sheds some light as to what this means for the scene, and also why people like math and geo were so reluctant to release these exploits. Peace...

Most helpfull post of today, thank you man