Huh? How would you do that? The only way to connect is to have your PC pretend to be Sony's authentication server. The SSL certificate that gets replaced in the PS3 lets it think that your PC is really $ony.
Charles Web Debugging prog performs the MITM by modifying the headers to change your f/w version to 3.56, and feeds the PS3 with a fake update_list that tells the PS3 that the current f/w is 3.21. So the PS3 connects. $ony can stop this in a second.
Good to see drizzt84 is still into it, although he got post from Sony lawsuit. This seems to be a very easy version how to do it, and no risk to brick instead of installing an other CFW. Will give it a shot this afternoon.
As long as you don't power off the PS3 you just do this once
1. Install the Two Packages. (Just click)
2. Launch the first one. (Just a click and It does the Mounting itself for you)
3. Launch the second one. (To manually rename a certificate takes seconds)
4. Set the DNS same as your PC IP. (Takes seconds)
5. Done. Now Reboot your PS3, Start PS3DNS.exe and Start FckPSN.exe. (You basically click a few buttons)
I'm sure he/she was refering only to the part of installing the cert file - simply by using a "dedicated" pkg file / app to do that (or even more advanced one which would alow you to toggle between original and replaced cert any time you want) rather than fiddling "manually" with ftp and so on. Then all you'd need to do would be to change your DNS settings and run 2 apps on your pc
Does anyone know HOW this works? In other words, will Sony be able to fix this instantly or with another update? Or is this a pretty bullet proof unfixable (for Sony) PSN workaround? Or in other other words, IS THIS A PERMANENT FIX?