- Sony Zwangsupdate umgehen: Firmware Check Bypass Beitrag #21
I
imported_Nightmare
- Dabei seit
- 01.04.2010
- Beiträge
- 7
- Punkte Reaktionen
- 0
Angeblich will sich die PS3 jetzt per https einloggen. Vielleicht hat Sony ihren Login-Server auf https umgeleitet.Dojokun schrieb:Ich wüsste nicht, wie die das verhindern wollen. Das geht nur durch ein weiteres FW-Update, in dem die die IP des Updateservers fest verdrahten und abprüfen.
Aber ich werde mal fix noch für alle Fälle das Updatefile sichern
Eigentlich gibt es aber doch genug Programme um https Datenverkehr aufzuschlüsseln per man-in-the-middle. Natürlich kann es aber sein das die Verbindung dann blockiert wird (?).
http://www.yellowdog-board.com/viewtopic.php?p=38085#p38085
Okay - so I did a little packet sniffing.
What I found is that, as I had mentioned, the PS3 checks to see what the current firmware is, and updates if necessary. This is done via http:// and is the basis of the DNS trick. Then, it tries to log into PSN via https:// , and this is where we fail now.
So - since I can't decrypt https:// packets that's the end of my snooping.
Cheers,
Paul
Neue Details von jtdc:
http://www.ps3news.com/forums/ps3-h...re-3-21-connect-psn-110382-19.html#post290052In a small way (in which experts know about this already), I did some sniffing of things going on the auth.np.ac.playstation.net:443 as that site does the authentication before allowing to login. There were various exchanges of certificates to and from that server to the console. Somehow it triggers some command where it extracts the infos of the console then sent for checking and outputs 8002A212 if not latest firmware. The commands and info exchange are all machine language and its visible that its verisign encrypted.
Its very elementary and easy if all strings with lower than 3.21 on the UserAgents are replaced correctly, but that will be useless because all the critical info exchange are in the encrypted streams. The bad thing about this is how, where, when, and what packets to inject therein because essentially its intruding on an encrypted data exchange.
I see that there is some checking in place also to verify the authenticity and integrity of the data being exchanged (there are several followup connections to the auth server), so the modification coming from data injection would be tricky and difficult.
Perhaps a way to get this is extract a successful handshake from a 3.21 running console and replicate it on a lower firmware console via packet injection. But then, its a whole new different console altogether, and probably the certificates would not match.
This challenge seems beyond my current skill, but again, if I can assist on anybody else here with better progress, I am in.