Originally posted by Siga
was pretty sure the cert files had a signature on them unique to the system , and the x-passphrase is the key its encrypted data sent to the ps3 allowing it to connect it doesnt give any info on how the phrase is now ps3 sends what fw and some other info like you know already so how are you faking this to the server which will have a sig check if it doesnt idk how no one has gotten back online yet , if you wish to continue please do so in a pm i do not wish to clutter your thread anymore
Heres what you do not know. During the time we HAD sp-int and such I was doing some research/snooping. I have done my fair share in hacking the PSN service

.
Anyways the x-passphrase is a HTTP header sent over an encrypted SSL connection. The ps3 f/w version is a header too. That or its the user agent (can't remember). The reason we were able to go online before was the fact that we spoofed the F/W version and the pass on-the-fly with charles and then the fuckPSN ruby script. We can't know exactly what is sent now but we can find out by simply decrypting the connection...
Once decrypted we can intercept all data and see all HTTP headers and data sent. It is then just a matter of getting a 3.55 PS3 to do the same via a mixture of editing the firmware SELF's and spoofing via MITM.
As a random thought, you can verify your claim about CERT having a sig by opening an original CERT in a hex editor and looking for data thats not part of a standard RSA/DSA BASE64 encoded cert. All files have the signature in a header data section in the file itself.
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
Originally posted by jack4au
you get homebrew on your 4.11 ps3 fromjust data transfer it just doesnt run
Data transfer transfers your hard disk, not your nand. Your NAND/NOR(depending on PS3 model) is a data microchip that contains the firmware/operating system for the ps3.