[SonsOfLiberty]

Originally Posted by Buggerlugz All this will lead to is the debug eboots, the people behind JB2 have re-encrypted being decrypted and then uploaded to the web without encryption so anyone can use them.

Maybe you should read around a bit before you say that :D Make sure you read it fully.

First, I have already read this whole thread and the dev wiki. I am aware of what you believe to be the "verified" facts. However, when the same misconceptions are repeated over and over by different people, it does not magically make them true. The fact that I just signed up to post here also has no bearing. I am a professional developer and I have personally messed with PS3 homebrew. From your posts, it is obvious to me that you do not have a proper grasp on many concepts including encryption, security and basic development principles. Therefore, I could argue that I am more qualified than you are to comment on this JB2 subject. You need to stop mentioning mathieulh - any real developer knows that this guy has no real skills and is simply an attention whore. If you want to see what I mean, check this tweet by the RESPECTED dev xorloser: http://twitter.com/#!/xorloser/status/22764585537 and then see how many others retweeted it. As further proof, lets look at his comments regarding JB2. First he claims to have figured it out after a "few minutes of debugging" (which I cant see how is even possible given he claims he does not actually have a dongle). He first claimed that they had 3.6+ keys on the dongle. Then he claimed that jb2 runs master discs with un-encrypted fself files (see the dev wiki), which totally contradicts his previous "findings". He even mocked them for not encrypting the eboots. This is especially funny considering that if you look at the JB2 eboots released, they are obviously encrypted. Then finally he claims via his twitter that they are in fact encrypted. So he's given you guys 3 different stories, all the while he doesnt even have access to a JB2 so **** knows how he came to these conclusions. Moral of the story, dont trust this guy - he simply doesnt know what he is talking about. Now back to the point at hand, if you're still following xPreatorianx. The stuff on the dev wiki has come for the most part from mathieulh, so personally I dont trust a word. For a start, if they really were using masterdisc encryption, you'd see decrypted dumps available. Thats because decrypting masterdiscs is EASY. It makes no sense for these guys to use such a trivial system when they could just as easily roll their own disc encryption and keep us on our toes. Nobody has confirmed they are using masterdisc encryption. If you dont believe me then fine, keep trying to decrypt these discs with the masterdisc algo, and have fun Your obsession with "FSELF" is cringe worthy as it has almost no relevance. As was pointed out by RikuKH3, FSELF is simply a container format for ELF files. SELF files are ALSO simply containers for ELF files. Do you understand? This means that underneath it all, its the same thing, ELF executables. SELF = Sony encrypted container for ELF files, FSELF = SELF minus the encryption. Now, a lot of homebrew has been released in FSELF format. JB, JB2 etc can all run FSELF files IN ADDITION to regular SELF files. Therefore, it would be convenient for JB2 to simply re-package their stuff as FSELF with their own encryption added on the top. This part is important, are you still following? FSELF IS SIMPLY A CONTAINER FORMAT AND HAS NOTHING TO DO WITH DEV PSN. Just because the eboots on JB2 discs are FSELF files does not imply that the source eboots have come from DEV PSN. JB2 guys could have easily converted any ELF file into a FSELF to use on their discs. Any SELF EBOOT for which they have keys to (including <= 3.56), they can convert to a FSELF file trivially. So PLEASE drop the crap about how this stuff must have come from DEV PSN. There is literally NOTHING at all to indicate that, and if you have properly understood my last post, you would realise that its much more likely that they have 3.6+ keys, decrypt SELF EBOOTS and re-package them as FSELF with their own crypto on top. From what I can make out, this whole thing with debug eboots came about simply because somebody noticed that they were using FSELF. As I already explained, this actually does not imply that they are using actual DEBUG eboots. So you guys have simply been propagating misinformation. xPreatorianx, I know you're only trying to help but you obviously have large holes in your understanding of this stuff. You are certainly NOT the authority on any of this so please in future stop acting as though you are.

http://tinyurl.com/7seot6k