Yes I am totally aware 100% of what you have stated. The reason I use quotes around "proxy" is because there is not going to be a middle man.
My program will let the PS3 connect directly to it, and capture the data from the PS3. It will not be sent to the server.
Then after the program has collected and created new data, the old data will be tossed (The reason is connects and doesn't send is so the PS3 will not disconnect. It will attempt to keep the connection open.)
I know various methods of cryptography and it's the SSL that breaks it with me.
After the creation of new data, the program itself will connect to the remote server. No middle-man here, or anywhere. It just throws away the PS3 data, and creates new data to send to the server, therefore the PS3 does not get cut off at any time. After data is received from the server side, the PS3 is alerted while the connection has been on hold (timeout at least 45 seconds)
Therefore it's not a true proxy, just a WAIT FOR REPLY kinda thing. It does no actual proxy work. It's to collect data from the PS3 and server and just sends BS to the server (On a separate thread+connection).
I can create a secure connection with the program already to the server. It's the PS3 I haven't tested yet because, well, (I'm not at home, still in Japan and waiting to crack mine open.)
But you do have valid points, I understand completely, but I haven't exactly told this stuff because I am afraid sony could patch it now that it's out in the open.